Check for 206 status on HEAD requests - #34
Merged
aadsm merged 1 commit intoApr 6, 2014
Merged
aadsm merged 1 commit into
aadsm merged 1 commit into
Conversation
Copy link
Copy Markdown
Owner
Sorry, something went wrong.
It seems that Firefox 28 is returning status code 206 when the file has been cached. This is odd because 206 stands for Partial Content which only makes sense for GET Range requests...
aadsm
added a commit
that referenced
this pull request
Apr 6, 2014
Check for 206 status on HEAD requests
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
It seems that Firefox 28 is returning status code 206 when the file has
been cached. This is odd because 206 stands for Partial Content
which only makes sense for GET Range requests...