Normal
This is related to the too many redirects problem and is a FindRetros bug.The problem is related to how IPs are handled and it looks like Findretros prioritizes the user's IPV6 over their IPV4. To account for this, your hotel should support IPV6s and prioritize it while also adding a second layer of vote tracking locally as a safe-guard. This could be as simple as setting a cookie or local storage flag of did-vote=yes[SPOILER="Old Thread"]I've have an issue on my hotel since enabling FindRetros support where users get stuck into endless redirect loops and tracked it down to an issue with FindRetros itself.When sending the correct IP Address of the user to Findretros, it will respond with a "user has not voted" state even after a successful vote.[ATTACH=full]16822[/ATTACH]This is my IP Address and I verified multiple websites were capable of producing the same IP.Is it the "legacy" voting API?Yes and no since the official SDK uses the same exact endpoint under the surface. The only difference being a cookie so you can track voting on your side outside of FindRetros which answers the question of why FindRetros has a redirect loop for some hotels and issues on others.[URL unfurl="true"]https://github.com/FindRetros/Vote-Validator/blob/master/findretros.php[/URL]What you can doAdd a mechanism for tracking if the user has voted in the last 24/h on your site on top of the FindRetros API. Ideally, you'd use Findretros as a last resort for tracking votes as it's not trustworthy.What should FindRetros doFix your IP tracking. IP Addresses are fairly consistent and if multiple sites match up, the problem is with you.[/SPOILER]
This is related to the too many redirects problem and is a FindRetros bug.
The problem is related to how IPs are handled and it looks like Findretros prioritizes the user's IPV6 over their IPV4.
To account for this, your hotel should support IPV6s and prioritize it while also adding a second layer of vote tracking locally as a safe-guard. This could be as simple as setting a cookie or local storage flag of did-vote=yes
[SPOILER="Old Thread"]
I've have an issue on my hotel since enabling FindRetros support where users get stuck into endless redirect loops and tracked it down to an issue with FindRetros itself.
When sending the correct IP Address of the user to Findretros, it will respond with a "user has not voted" state even after a successful vote.
[ATTACH=full]16822[/ATTACH]
This is my IP Address and I verified multiple websites were capable of producing the same IP.
Is it the "legacy" voting API?
Yes and no since the official SDK uses the same exact endpoint under the surface. The only difference being a cookie so you can track voting on your side outside of FindRetros which answers the question of why FindRetros has a redirect loop for some hotels and issues on others.
[URL unfurl="true"]https://github.com/FindRetros/Vote-Validator/blob/master/findretros.php[/URL]
What you can do
Add a mechanism for tracking if the user has voted in the last 24/h on your site on top of the FindRetros API. Ideally, you'd use Findretros as a last resort for tracking votes as it's not trustworthy.
What should FindRetros do
Fix your IP tracking. IP Addresses are fairly consistent and if multiple sites match up, the problem is with you.
[/SPOILER]