We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
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:
FlyingFox/FlyingFox/Sources/HTTPConnection.swift
Line 122 in ed86fc6
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 :)
The text was updated successfully, but these errors were encountered:
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?
Sorry, something went wrong.
No branches or pull requests
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:
FlyingFox/FlyingFox/Sources/HTTPConnection.swift
Line 122 in ed86fc6
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 :)
The text was updated successfully, but these errors were encountered: