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
{{ message }}
This repository has been archived by the owner on Dec 13, 2018. It is now read-only.
the-overengineer
changed the title
Login form does not safe encode next query parameter
Login form does not safe encode next query parameter
Feb 10, 2017
In the Login form when the user needs to be authenticated, the
next
query parameter does is not URI encoded with encodeURIComponent.Example
request
/resource?pretty&test=1
Authentication Failed
redirect
login?next=/resource?pretty&test=1
However the redirect should be
redirect
login?next=%2Fresource%3Fpretty%26test%3D1
Proposed change: Add encodeURIComponent when setting next, and decodeURIComponent when redirecting after successful login
Currently, the original query parameters after the first one does not get included when redirected
The text was updated successfully, but these errors were encountered: