Open zltnDC opened 1 year ago
I was migrating an HTTP Server to FlyingFox and I encountered a client side error "Socket write failed". I spent some time to discover this line:
https://github.com/swhitty/FlyingFox/blob/ed86fc6d68ec1467aaab3e494b581e66dd7a4512/FlyingFox/Sources/HTTPConnection.swift#L122
The client app didn't send the "keepalive" header in requests. I think it would be great to mention "keepalive" in readme.
Thank you for this great lightweight server :)
Do you think this is a bug where clients do not send Connection: keep-alive and FlyingFox is closing the connection too early?
Connection: keep-alive
Out of interest which HTTP Client were you using?
I was migrating an HTTP Server to FlyingFox and I encountered a client side error "Socket write failed". I spent some time to discover this line:
https://github.com/swhitty/FlyingFox/blob/ed86fc6d68ec1467aaab3e494b581e66dd7a4512/FlyingFox/Sources/HTTPConnection.swift#L122
The client app didn't send the "keepalive" header in requests. I think it would be great to mention "keepalive" in readme.
Thank you for this great lightweight server :)