I've observed a similar interruption issue in the FPC HTTP client on
Windows.
After a server-timeout the client stream is corrupted. I observed it
during server debugging.
If I am not mistaken, the steps-to-reproduce are:
The client sends a request -> the server takes too long to respond (e.g.
because I debug the request on the server) -> client shuts down with
timeout -> server finishes the request -> client sends a new request ->
the client reads wrong data (maybe old data are on the socket, I don't
know yet).
I have wanted to debug and fix the issue for a long time but haven't
found the time to do so. I still have to check the
exact steps-to-reproduce... Hopefully I'll do it soon :)
Ondrej
_______________________________________________
fpc-pascal maillist - [email protected]
https://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-pascal
