nginx and uwsgi: upstream sent too big header while reading response header from upstream

[Johann Spies]

This error is giving met a lot of trouble. 

I have read about solutions using something like

fastcgi_buffers 8 256k;
fastcgi_buffer_size 128k;   

where nginx is using fastcgi, but I am working with uwsgi and this does not help me.

Am I the only web2py user with this problem? 

I will be glad to hear about solutions from other web2py-users.

Regards
Johann

--
Because experiencing your loyal love is better than life itself,
my lips will praise you.  (Psalm 63:3)

[Roberto De Ioris]

> This error is giving met a lot of trouble.
>
> I have read about solutions using something like
>
> fastcgi_buffers 8 256k;
> fastcgi_buffer_size 128k;
>
> where nginx is using fastcgi, but I am working with uwsgi and this does
> not
> help me.
>
> Am I the only web2py user with this problem?
>
> I will be glad to hear about solutions from other web2py-users.
>
> Regards
> Johann

nginx buffers can be set for all of the supported protocols:

http://wiki.nginx.org/HttpUwsgiModule#uwsgi_buffer_size


--
Roberto De Ioris
http://unbit.it

[Johann Spies]

Thanks.

Regards
Johann

--
Resources:
- http://web2py.com
- http://web2py.com/book (Documentation)
- http://github.com/web2py/web2py (Source code)
- https://code.google.com/p/web2py/issues/list (Report Issues)
---
You received this message because you are subscribed to the Google Groups "web2py-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to web2py+un...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Casey S. Schroeder]

Johann,

I know it was some time ago, but were you able to fix this problem?  We are encountering something similar, and I'm concerned it may have to do with where we are placing the nginx commands.

Thanks

[Massimo Di Pierro]

You should not use fastcgi. I do not think anybody uses that any more. you should use nginx+uwsgi.