{"push_id":1052209498,"size":1,"distinct_size":1,"ref":"refs/heads/bugfix/urlencode-next","head":"5a935da4b2bb7188831fc6ca53e6f9e482506cb0","before":"35506272e23862d83b76bb234efd1ca16e32f150","commits":[{"sha":"5a935da4b2bb7188831fc6ca53e6f9e482506cb0","author":{"email":"1a73af9e7ae00182733b2292511b814be66f065f@eleni.co","name":"Eleni Lixourioti"},"message":"Fix `next` query param encoding and resolution.\n\nFixes issue #12: https://github.com/yunojuno/django-perimeter/issues/12\n\nThere was a reported problem when authenticating on the gateway\nand the `next` param contained a query string, in which case\nthe redirect location would drop said query string.\n\nThis changeset addresses 3 related issues:\n* The `next` param is now fully urlencoded (both the path and the query string, if any).\n* The query string compoment of the path, which was dropped in the middleware, is now maintained.\n* The `resolve` function doesn't like query strings, so when we check\nthat a url exists we temporarily drop the query string.","distinct":true,"url":"https://api.github.com/repos/yunojuno/django-perimeter/commits/5a935da4b2bb7188831fc6ca53e6f9e482506cb0"}]}