Skip to content
New issue

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

Hangs on HEAD requests with null response body #10

Open
duncanpierce opened this issue Apr 25, 2012 · 0 comments
Open

Hangs on HEAD requests with null response body #10

duncanpierce opened this issue Apr 25, 2012 · 0 comments

Comments

@duncanpierce
Copy link

Hi Louis,

I've been working on an OWIN-based app that needs to respond to HEAD requests. By the HTTP/1.1 spec a HEAD request must not have a response body but the headers should be the same as if it were a GET request.

With keep-alive connections, Firefly hangs (as of 7d3492e) when I pass a null response body. Passing a null body is allowed for by the draft 5 OWIN spec and is required when hosting on Kayak. I think it makes sense for Firefly to handle a null response body.

Passing a body which just calls end(null) works, so for now I've implemented a small middleware component for running with Firefly.

Many thanks for Firefly - it's proving very useful for testing my async handling and I'm getting good performance from it.
Duncan

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant