-
Notifications
You must be signed in to change notification settings - Fork 3.6k
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
Don't call WriteHeader more than once #33
Comments
I don't think this is happening anymore. Closing for now. |
this bug still exists (or came back), I am not sure how I triggered it but each time I do a get request my console is flooded by this warning (I am running on master). Edit: I don't have it with 0.4.0 though |
I spoke too quickly now I have it on 0.4.0 too, I am not sure but it seems linked to parallel requests. |
@schmurfy Thanks for the update. Reopening this and we'll take a look! |
I get back the no response part, otherwise I tried to narrow down when exactly I get the warning but the end result is.. I have no idea xD |
I get this often when I send an invalid time format. |
Do you still get it with the fix that i just pushed ? On Thu, Jan 23, 2014 at 5:33 PM, Michael Crosby notifications@github.comwrote:
|
@jvshahid Sorry, i didn't refresh the issue before posing the comment. I'll test tonight. |
I'll try to test it too and report here. |
Check checksum before load snapshot
This message is all over the logs:
We shouldn't be calling WriteHeader more than once.
The text was updated successfully, but these errors were encountered: