{"push_id":815565490,"size":2,"distinct_size":2,"ref":"refs/heads/master","head":"f11788bed194a68aa6118f5c4fc47948fb79ea19","before":"166b4e2b5da706313ca3d2d4ac4ca51e11855965","commits":[{"sha":"e17367b4e5f865db4947fc4139baa0974d4a7326","author":{"email":"e186a7d2c4e55136cd884424bcfb439491001dc6@byte.nl","name":"Maarten van Schaik"},"message":"Fix redirect_uri issue with tornado reversed url\n\nWhen reversing URLs, tornado doesn't interpret the regex optional symbol\n'?'. This causes the redirect_uri to be\nhttps://example.com/complete/mybackend/? with the question mark\nappended. Some providers will simply append to this uri, causing URLs\nlike https://example.com/complete/mybackend/??code=.... with two\nquestion marks. This makes the interpretation of the query string fail.\n\nThe provider in this case is\nhttps://github.com/juanifioren/django-oidc-provider. Arguably that\nlibrary should be smarter in constructing the redirection, but removing\nthe question mark from the uri solves these kind of issues.\n\nAlternatively we could strip the question mark from the uri in the\ntornado strategy, but this seemed simpler.","distinct":true,"url":"https://api.github.com/repos/omab/python-social-auth/commits/e17367b4e5f865db4947fc4139baa0974d4a7326"},{"sha":"f11788bed194a68aa6118f5c4fc47948fb79ea19","author":{"email":"249b764bb8edfa93c5fe70f291749c56f0d2f1f6@gmail.com","name":"Matías Aguirre"},"message":"Merge pull request #674 from ByteInternet/fix-tornado-redirect-uri\n\nFix redirect_uri issue with tornado reversed url","distinct":true,"url":"https://api.github.com/repos/omab/python-social-auth/commits/f11788bed194a68aa6118f5c4fc47948fb79ea19"}]}