[Libwebsockets] Is there a limit on the path size?
andy at warmcat.com
Fri Nov 18 22:57:31 CET 2016
On November 19, 2016 3:59:24 AM GMT+08:00, Stephen James <sajames1958 at gmail.com> wrote:
>This path works find on my browser, but I cannot get it to work on test
1) if you're literally using the test client, he doesn't expect such a long path and needs adapting
2) If it's still truncated, you can tune the max header content size limit at context creation time
/**< CONTEXT: The max amount of header payload that can be handled
* in an http request (unrecognized header payload is dropped) */
in v2.1 this became 4K, but previously it was 1K.
3) In this case the request packet is composed into the service thread's pt buffer, so that also must be larger than the entire header (default 4096), and can also be tuned at context creation time
unsigned int pt_serv_buf_size;
/**< CONTEXT: 0 = default of 4096. This buffer is used by
* various service related features including file serving, it
* defines the max chunk of file that can be sent at once.
* At the risk of lws having to buffer failed large sends, it
* can be increased to, eg, 128KiB to improve throughput. */
>Libwebsockets mailing list
>Libwebsockets at ml.libwebsockets.org
More information about the Libwebsockets