Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

upstream sent too big header while reading response header from upstream #527

Closed
adilnaimi opened this issue Feb 20, 2015 · 3 comments
Closed

Comments

@adilnaimi
Copy link

Hi,

we use django+nginx and third nginx reverse proxy in the front.

Google auth2 fails because of the too big header sending from reverse proxy to the nginx+django layer.

Could you help please

@ahmedouvic
Copy link

This is fixed here f138221

@adilnaimi
Copy link
Author

If you have nginx error 502, try to add to nginx config file the following buffer setup:

http {

        .....
        .....

        proxy_buffer_size 128k;
        proxy_buffers 4 256k;
        proxy_busy_buffers_size 256k;

        .....

@omab
Copy link
Owner

omab commented Apr 4, 2015

This doesn't seem to be a problem with python-social-auth but just something with your setup, right?

@omab omab closed this as completed Apr 4, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants