Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Force the use of cookies #325

Closed
GoogleCodeExporter opened this issue Mar 25, 2015 · 3 comments
Closed

Force the use of cookies #325

GoogleCodeExporter opened this issue Mar 25, 2015 · 3 comments

Comments

@GoogleCodeExporter
Copy link

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

@GoogleCodeExporter
Copy link
Author

Original comment by renggli on 8 Sep 2009 at 7:09

  • Added labels: Version-Seaside3.0
  • Removed labels: ****

@GoogleCodeExporter
Copy link
Author

Original comment by renggli on 8 Sep 2009 at 7:10

  • Added labels: ****
  • Removed labels: Version-Seaside2.9

@GoogleCodeExporter
Copy link
Author

WACookieOnlySessionTrackingStrategy does this

Original comment by [email protected] on 2 Aug 2011 at 7:14

  • Changed state: Fixed
  • Added labels: Version-Seaside3.1
  • Removed labels: Version-Seaside3.0

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant