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 Jan 24, 2019. It is now read-only.
However, I have noticed an issue or not...
Lets say I made a PUT request to my nginx, request hands to oauth2_proxy for authentication/authorization.
When oauth2_proxy finishes (validating access token, refresh token, etc...), it redirect back to nginx but now with a 'GET' instead of 'PUT'.
Is this normal? a feature?
Thanks
The text was updated successfully, but these errors were encountered:
The first request from browser which is not already "logged-in" to oauth2_proxy will go through the oauth2 flow and end up with a redirect back to the original destination, with method changed to GET (and no body, of course).
Subsequent requests will carry the cookie which oauth2_proxy will recognize, and the PUT will go through to the backend service unchanged.
If you're using the nginx auth_request directive, it's a bit more complicated: the auth request to oauth2_proxy will not include the body, but will have the original Content-Length header, which will confuse oauth2_proxy into waiting for a body which will not come. The README has the nginx config options to correct for this.
I got oath2_proxy working with openresty/nginx.
However, I have noticed an issue or not...
Lets say I made a PUT request to my nginx, request hands to oauth2_proxy for authentication/authorization.
When oauth2_proxy finishes (validating access token, refresh token, etc...), it redirect back to nginx but now with a 'GET' instead of 'PUT'.
Is this normal? a feature?
Thanks
The text was updated successfully, but these errors were encountered: