> -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA512 > > Op 24-01-12 21:16, Roberto De Ioris schreef: >> Expect 100-continue has been implemented in latest tip. As it is a >> feature you may want to implement in the app itself (instead of >> the http server/router), you have to enable it with >> --http-manage-expect > > Actually the only thing I wanted to know what caused this. In your > previous mail you said it was actually curl doing this. Still that > doesn't make sense if post-buffering isn't enabled, when it doesn't fail.
Expect-continue has nothing to do with post-buffering. It is an extesion to the HTTP protocol for checking if a webserver will accept the body (before sending it). If your app does not honour it, the proxy should do it (but it is not mandatory, and infact curl will stop waiting for it after 1 sec) This is the relevant thread in the official WSGI list: http://mail.python.org/pipermail/web-sig/2008-January/003186.html This is practically what curl with -T does: - send request - send headers (with expect) - wait for expect response (max 1 second) - after 1 sec (or if the server respond) send the body to the http router - the http router receives it and forward to uwsgi worker With the new implementation (adding --http-manage-expect) the http router will send an expect confirmation automatically. It is actually practically useless, but we could use it in the future to support settings limits on content-length -- Roberto De Ioris http://unbit.it _______________________________________________ uWSGI mailing list [email protected] http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
