I'm trying to improve POST performance from cURL for applications
behind uWSGI (using the builting uWSGI HTTP server via the http-socket
option), and I'm running into the dreaded "Expect: 100-continue"
issue. Unfortunately, getting all clients to invoke curl without the
expect header is not an option. I tried setting the
"http-manage-expect" configuration option to various values ("true",
1, and 10000), but uWSGI never actually sends the "100 Continue"
response. Is there something else I need to set in order for
http-manage-expect to work with http-socket?
Barring http-manage-expect, I've set up the following routing rule to
do it myself:
route-if = contains:${HTTP_EXPECT};100-continue send-crnl:HTTP/1.1 100 Continue
route-if = contains:${HTTP_EXPECT};100-continue send-crnl:
On a scale of 1 to 10, how terrible of an idea is it to deploy this rule?
--
James Brown
Engineer
_______________________________________________
uWSGI mailing list
[email protected]
http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
