You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This came out of discussion in Issue 304.
It might be nice to have a setting to force the use of cookies in your
application. This would ensure that URLs were never written containing the
session key.
This could possibly be done in WARegistry>>addCookieForHandler:to: by
forcing a redirect with a "cookieTest" field in the URL and then catching
incoming requests with "cookieTest" set but no cookie and responding with
an error.
Rather than having a new setting for this, #useCookies could possibly be
changed to a select box with "no/yes/force" or similar as options. This
would ensure nonsensical combinations.
Original issue reported on code.google.com by [email protected] on 30 Jan 2009 at 2:56
The text was updated successfully, but these errors were encountered:
Original issue reported on code.google.com by
[email protected]
on 30 Jan 2009 at 2:56The text was updated successfully, but these errors were encountered: