Jim Zhan <[email protected]> wrote: > Hi Eric, > > Thank you for the quick reply. I checked out hosts and we are using Unicorn > 3.4.1. Unfortunately there is only one setting for client_body_buffer_size. > So how does this parameter work? Will it only put a limitation on the body > itself or it applied proportionally to header and body (e.g., header 8k, > body 104k, etc).
client_body_buffer_size in unicorn is only for request bodies (uploads), and not relevant to header sizes. > We did experiments using curl by sending header exceeding 8k manually and I > am getting 404. So it's unicorn itself, not nginx that has the 8k header > size limitation. I suspect you're hitting the nginx large_client_header_buffers default limit of 8K: http://nginx.org/en/docs/http/ngx_http_core_module.html#large_client_header_buffers I checked the unicorn source, and ext/unicorn_http/global_variables.h defines the maximum field value as 80K, 10 times more than what you're seeing: DEF_MAX_LENGTH(FIELD_VALUE, 80 * 1024); This value was inherited from Mongrel many years ago and never changed. > The command we used for the experiment: > curl -v -H "$(./http-header-pumper.bat 8000)" <service_url> I just tried your script with the following config.ru to hit unicorn directly (no nginx), and I got the expected lobster response. $ unicorn -E none config.ru ----------- config.ru ----------- require 'rack/lobster' use Rack::ContentLength run Rack::Lobster.new --------------------------------
