Hi,
> The second response is a response to an expected follow up request on
> the same connection (using keep alive). If you're seeing it as part of
> the response on the first request then it's either an issue with the
> client not handling keep alive connections correctly, or an issue with
> the
The second response is a response to an expected follow up request on
the same connection (using keep alive). If you're seeing it as part of
the response on the first request then it's either an issue with the
client not handling keep alive connections correctly, or an issue with
the content length
Hi,
We're testing the civetweb frontend currently and there is an
intermitent issue where the response will contain an extraneous 'ERROR
500' response mixed in.
This is a tcpdump from such an occurent.
-
GET / HTTP/1.1
User-Agent: curl/7.30.0
Host: s3.svc:81
Accept: */*
HTTP/1.1 200 OK
Co
