Reply to thread

Message

<blockquote data-quote="RastaLulz" data-source="post: 416478" data-attributes="member: 1">It will continue to be supported for the foreseeable future; there is currently no replacement. &quot;validate.php&quot; was added back since some applications wouldn't follow the redirect to &quot;/legacy/validate&quot;.You should always check to see if a user has voted for redirecting them. Otherwise you open up yourself to redirecting your users to a site that is down. Setting a cookie is advised, especially for bigger hotels. I don't know if it'd actually cause issues, as I'm pretty sure those in the past were caused by hotels that would send a request to FindRetros every time they updated the user count on the client, which was a problem. You should always send the user with the &quot;return&quot; query arg set, as that will guarantee that they are sent back to the &quot;return_url&quot;.I'd love to hear if anyone is having issues as well, feel free to post in this thread.</blockquote>

[QUOTE="RastaLulz, post: 416478, member: 1"] It will continue to be supported for the foreseeable future; there is currently no replacement. "validate.php" was added back since some applications wouldn't follow the redirect to "/legacy/validate". You should always check to see if a user has voted for redirecting them. Otherwise you open up yourself to redirecting your users to a site that is down. Setting a cookie is advised, especially for bigger hotels. I don't know if it'd actually cause issues, as I'm pretty sure those in the past were caused by hotels that would send a request to FindRetros every time they updated the user count on the client, which was a problem. You should always send the user with the "return" query arg set, as that will guarantee that they are sent back to the "return_url". I'd love to hear if anyone is having issues as well, feel free to post in this thread. [/QUOTE]

Verification

Reply to thread

Connect with us

Newest members