Roberto De Ioris <roberto@...> writes: > Check the last line of http://projects.unbit.it/uwsgi/wiki/ThingsToKnow
Darn, I read that a couple of times when we set it up. Of course, that's a long time ago now. > nginx has a 4k limit buffer (auto-tunable to 8k) for the request headers, > uWSGI has 4k by default, but not auto-tunable (but raisable upto 64k) > > You have to choose the 'best' value for your app. In your case i would > have used 8192 for being more nginx-friendly. Okay. I'll set it to 8k then. I had difficulty finding any docs in the nginx end. There's no negotiation step in the protocol where this limit could have been agreed upon between nginx and uWSGI? > If you are asking yourself why such limits exist, take in accounts headers > must be available for the whole request management, so you have to put > them in memory. Now just immagine an evil-users send a request with > thousand of headers :) I was sort of expecting this - but don't you think the appropriate setting should have a more suggestive name then, like max-request-header-size? It also worries me a bit that a normal user can hit this limit with normal size URLs, although apparently a bunch of cookies. I'm not sure why he had so big cookies, it was a left-over from their old CMS system made by someone else, but IIRC up to 4k cookies is considered okay by browsers. Thanks for the prompt response, by the way. :) Ole _______________________________________________ uWSGI mailing list [email protected] http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
