There are some statically defined limits defined in the http11.c and in some (rare) cases they are to small. The constants I am talking about are the following:
DEF_MAX_LENGTH(FIELD_NAME, 256);
DEF_MAX_LENGTH(FIELD_VALUE, 80 * 1024);
DEF_MAX_LENGTH(REQUEST_URI, 1024 * 36);
DEF_MAX_LENGTH(FRAGMENT, 1024); /* Don't know if this length is specified somewhere or not /
DEF_MAX_LENGTH(REQUEST_PATH, 1024);
DEF_MAX_LENGTH(QUERY_STRING, (1024 * 30));
DEF_MAX_LENGTH(HEADER, (1024 \ (80 + 32)));
It would be handy of this settings would have these sane default, but also be exposed as configuration parameters for those rare cases when higher limits are needed.
That part of the code is also shared by Thin and Unicorn, so they inherit the same "problem".
There are some statically defined limits defined in the http11.c and in some (rare) cases they are to small. The constants I am talking about are the following:
DEF_MAX_LENGTH(FIELD_NAME, 256); DEF_MAX_LENGTH(FIELD_VALUE, 80 * 1024); DEF_MAX_LENGTH(REQUEST_URI, 1024 * 36); DEF_MAX_LENGTH(FRAGMENT, 1024); /* Don't know if this length is specified somewhere or not / DEF_MAX_LENGTH(REQUEST_PATH, 1024); DEF_MAX_LENGTH(QUERY_STRING, (1024 * 30)); DEF_MAX_LENGTH(HEADER, (1024 \ (80 + 32)));
It would be handy of this settings would have these sane default, but also be exposed as configuration parameters for those rare cases when higher limits are needed.
That part of the code is also shared by Thin and Unicorn, so they inherit the same "problem".