Hello,
small MTU can be overridden by TCP_MSS I believe. The default 536 is very
small for POST indeed.
Adam
út 4. 2. 2020 v 13:41 odesílatel Trampas Stern napsal:
> The post parsing in the http code has couple problems. Most of the time
> it will not cause issues.
>
> First it assume the f
The post parsing in the http code has couple problems. Most of the time it
will not cause issues.
First it assume the first packet includes the entire POST header. With
small MTU size this might not happen.
Second it adds a null terminator at the end of the POST header before
calling httpd_post_
My observation is that httpd_post_receive_data is called for each received
packet until content_len for this connection is reached. Then the
httpd_post_finished is called for application to finalize.
--
Sent from: http://lwip.100.n7.nabble.com/lwip-users-f3.html
What happens if the MTU size is less than the header size? Specifically,
does the httpd.c code cache the packets and fill a buffer for header until
the complete header has been received before calling http_post_begin()?
>From looking at the data transfer it appears that the null terminator is
add
Trampas Stern wrote:
>I was trying to use the httpd.c example which does some POST data
>parsing.
>From the httpd.h file it appears that httpd_post_begin() function is
>called
>with the first packet of data. However in reality it appears in use
>that
>it is usually called with just the POST head
I was trying to use the httpd.c example which does some POST data parsing.
>From the httpd.h file it appears that httpd_post_begin() function is called
with the first packet of data. However in reality it appears in use that
it is usually called with just the POST header.
Since I assume the POST h
