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

return_to named parameter and Apache #92

Closed
thegallagher opened this issue Nov 29, 2012 · 3 comments
Closed

return_to named parameter and Apache #92

thegallagher opened this issue Nov 29, 2012 · 3 comments

Comments

@thegallagher
Copy link

In many Apache configurations (since this is the default value), Apache will refuse any request which contains a URL encoded forward slash in the path component of a URL (see AllowEncodedSlashes Directive).

Given this limitation, it is pretty much impossible to use the return_to named parameter on the above configuration. I realise that you can achieve almost the same result using Auth.redirect session variable, but sessions time out and this can cause confusion to end users. I also realise that the controller can be overridden, but if the functionality is there, it makes sense that it be compatible with most configurations.

I propose that in addition to checking for the return_to named parameter (for backwards compatibility), a query string parameter should also be checked. Perhaps someone else has a better solution.

This is just a suggestion. Maybe no one else has ever had this issue in which case it wouldn't make sense to add this given this is a limitation on a specific setup (albeit a common setup).

@thegallagher
Copy link
Author

Also just noticed that if you are unsuccessful in logging in then the return_to parameter is not preserved. I guess this is a separate issue though.

@burzum
Copy link

burzum commented Nov 29, 2012

Good point, we'll figure something out. I don't have a better idea either right now.

@burzum
Copy link

burzum commented Jul 28, 2014

Fixed.

@burzum burzum closed this as completed Jul 28, 2014
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

2 participants