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

WARestfulComponentFilter does not check for expired sessions #794

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

Comments

@GoogleCodeExporter
Copy link

WARestfulComponentFilter does not check for expired sessions, it always assumes 
when there is a session id that the session will also exist. This is not the 
case for expired sessions in which case the REST methods should be executed.

Original issue reported on code.google.com by philippe...@gmail.com on 1 Jun 2014 at 4:01

@GoogleCodeExporter
Copy link
Author

Name: Seaside-REST-Core-pmm.55
Author: pmm
Time: 1 June 2014, 6:05:06 pm
UUID: 3cc6451c-b7ba-4e10-8456-65167aa37609
Ancestors: Seaside-REST-Core-pmm.54

Issue 794:  WARestfulComponentFilter does not check for expired sessions
https://code.google.com/p/seaside/issues/detail?id=794

Original comment by philippe...@gmail.com on 1 Jun 2014 at 4:05

  • Added labels: ****
  • Removed labels: ****

@GoogleCodeExporter
Copy link
Author

Hi Philippe, any reason why this one is not closed? 

Original comment by jo...@yesplan.be on 28 Jul 2014 at 7:03

  • Added labels: ****
  • Removed labels: ****

@GoogleCodeExporter
Copy link
Author

Other than oversight? No.

Original comment by philippe...@gmail.com on 30 Jul 2014 at 6:49

  • Changed state: Fixed
  • Added labels: ****
  • Removed labels: ****

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