HTTP 1.1 processes requests in-order. Clients may send us additional
requests on the same TCP connection, but MHD will only ever look at a
subsequent request after processing the previous request is complete.
I hope this clarifies.
On 08/29/2018 09:43 AM, Kunal Ekawde wrote:
> Ahh ok, getting it
Hi Christian ,
How does this work with pipe-lining? My understanding was that the server
would still read the request but will maintain the order of response. But,
from your email it seems the server would also not read the second request
before sending a reply to the first request> ?
Is this co
Hi Santos,
MHD simply doesn't read the next request (at least not intentionally,
bits may end up in our read buffer but won't be looked at). But the
kernels may already buffer subsequent requests.
Happy hacking!
Christian
On 09/03/2018 10:30 AM, Santos Das wrote:
> Hi Christian ,
>
> How does
Hi,
I am using mhd as a restful server as well as handling websockets via the
connection upgrade mechanism that mhd utilises.
The initial handshake, where I interpret a particular GET request and add a
responce denoted with MHD_HTTP_HEADER_UPGRADE to state that it should be
upgraded.
The c
