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.
This might be more of an "FYI" than a bug - but I thought it was worth noting.
I've just had an issue pointing the proxy at Nginx (running mediawiki and php5-fpm).
On a small percentage of requests, I'd receive this error from oauth2_proxy. It mostly occurred on reloads (which probably meant that if-modified-since request was being sent - which might return a blank body):
http: proxy error: malformed HTTP response ""
After some debugging, I found that turning off keepalives on the "upstream" nginx solved the problem:
/etc/nginx/sites-available/whatever-upstream:
keepalive_timeout 0;
I've got a network dump that appears to include nginx responding with an extraneous blank line in the 304 not modified response. I'm not sure if there's anything oauth2 proxy can do to ignore this, or if I should be logging something with the nginx folk... :)
@oskarpearson Thanks for taking the time to report this. It's also to me why this might be happening, but i'll try to do some investigating in case this is a problem on the oauth2_proxy side.
Hi
This might be more of an "FYI" than a bug - but I thought it was worth noting.
I've just had an issue pointing the proxy at Nginx (running mediawiki and php5-fpm).
On a small percentage of requests, I'd receive this error from oauth2_proxy. It mostly occurred on reloads (which probably meant that if-modified-since request was being sent - which might return a blank body):
After some debugging, I found that turning off keepalives on the "upstream" nginx solved the problem:
/etc/nginx/sites-available/whatever-upstream:
I've got a network dump that appears to include nginx responding with an extraneous blank line in the 304 not modified response. I'm not sure if there's anything oauth2 proxy can do to ignore this, or if I should be logging something with the nginx folk... :)
Version info:
The text was updated successfully, but these errors were encountered: