>Does the zero-size is reported by uWSGI logs or nginx one ?
Yes, it is. Here is the uWSGI log entry:
{address space usage: 185155584 bytes/176MB} {rss usage: 42397696
bytes/40MB} [pid: 2581|app: 0|req: 14/14] 127.0.0.1 () {44 vars in 782
bytes} [Mon May 23 10:56:11 2011] GET /NotExistedPageTest => generated 0
bytes in 28 msecs (HTTP/1.1 404) 4 headers in 130 bytes (1 switches on core
0)
Also, I have checked my app_iter return value (it's actually a list with a
single element - an instance of <class 'webhelpers.html.builder.literal'>)
and headers list from webob.Response object within my application, and they
have reported correct size and content:
[('Content-Type', 'text/html; charset=UTF-8'), ('Pragma', 'no-cache'),
('Cache-Control', 'no-cache'), ('Content-Length', '559')]
> If uWSGI log reports the correct size, check this nginx option:
>http://wiki.nginx.org/HttpUwsgiModule#uwsgi_intercept_errors
I have tried, and it didn't helped.
On Mon, May 23, 2011 at 10:44 AM, Roberto De Ioris <[email protected]> wrote:
>
> > Hello!
> > I have a Pylons-based wsgi-app with a decorated 40x and 50x error pages.
> > When it had been deployed via CherryPyWSGIServer, these error pages were
> > OK.
> > Recently I migrated the application to uWSGI (0.9.7.2, Python 2.7.1), and
> > now the 40x and 50x responses return zero-length response bodies. I
> didn't
> > change anything in my code except the nginx proxy configuration params.
> > Here
> > they are:
> >
> > ## CherryPy configuration
> > ## ---------------------------
> > #proxy_pass http://127.0.0.1:8080;
> > #proxy_redirect off;
> > #proxy_set_header Host $host;
> > #proxy_set_header X-Real-IP $remote_addr;
> >
> > # uWSGI configuration
> > # ---------------------------
> > uwsgi_param QUERY_STRING $query_string;
> > uwsgi_param REQUEST_METHOD $request_method;
> > uwsgi_param CONTENT_TYPE $content_type;
> > uwsgi_param CONTENT_LENGTH $content_length;
> >
> > uwsgi_param REQUEST_URI $request_uri;
> > uwsgi_param PATH_INFO $document_uri;
> > uwsgi_param DOCUMENT_ROOT $document_root;
> > uwsgi_param SERVER_PROTOCOL $server_protocol;
> >
> > uwsgi_param REMOTE_ADDR $remote_addr;
> > uwsgi_param REMOTE_PORT $remote_port;
> > uwsgi_param SERVER_PORT $server_port;
> > uwsgi_param SERVER_NAME $server_name;
> > uwsgi_pass unix:/tmp/uwsgi_project_socket.sock;
> > uwsgi_param SCRIPT_NAME "";
> >
> > So, how to retain the previous behaviour of my error pages?
> >
>
> Does the zero-size is reported by uWSGI logs or nginx one ?
>
> If uWSGI log reports the correct size, check this nginx option:
>
> http://wiki.nginx.org/HttpUwsgiModule#uwsgi_intercept_errors
>
> probably nginx is intercepting errors
>
> --
> Roberto De Ioris
> http://unbit.it
> _______________________________________________
> uWSGI mailing list
> [email protected]
> http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
>
_______________________________________________
uWSGI mailing list
[email protected]
http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
