> > > ----- Oryginalna wiadomoÅÄ ----- >> Od: "Roberto De Ioris" <[email protected]> >> Do: "uWSGI developers and users list" <[email protected]> >> WysÅane: piÄ tek, 11 marzec 2011 11:29:13 >> Temat: Re: [uWSGI] cacheframework >> >> Are you sure you are putting valid HTTP response in the cache ? >> >> Otherwise nginx will discard data >> > > I swapped the current: > uwsgi.cache_set('x', '1234') > > to: > wsgi.cache_set('x', 'HTTP/1.1 200 OK\nContent-Type: text/html; > charset=UTF-8\n\n1234\n') > > Only thing that has changed is that it immediately corresponds with 502: > $ curl -I http://t3/c/ > HTTP/1.1 502 Bad Gateway > Server: nginx > Date: Fri, 11 Mar 2011 10:36:13 GMT > Content-Type: text/html > Content-Length: 166 > Connection: keep-alive > > > before - hung up to nginx timeout.
Sorry, i always use uwsgi_param get "key"; instead of uwsgi_param key "key"; so i did not notice a stupid bug in "key" manager. This is fixed in latest tip. As in the doc is not reported, the difference between key and get is in the second returning a valid http not found error when data is not available (key will brutally close the connection) > -- Roberto De Ioris http://unbit.it _______________________________________________ uWSGI mailing list [email protected] http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
