we have a few HTTP endpoints that have very large request payloads (headers + 
query string).  They’re all oAuth endpoints coming in from 3rd parties, with a 
bunch of header data and a super long query string.  

the quick fix was to double buffer-size to 8192

is this the best approach?

also, it might be worth adding to the “ThinkToKnow” docs that if you’re doing 
anything with oAuth against twitter or Facebook, you should increase the buffer 
size.  one (or more) platforms had some recent change where they either 
increased logging headers or increased their key size, and the payloads jumped 
to just-over 4100 bytes.
uWSGI mailing list

Reply via email to