Changed accept-encoding header to identity #56
Merged
Conversation
This file contains 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
The compress module on the node connect server doesn't seem to honor q=0 on gzip, so to make the proxy work with connect, I had to change the accept-encoding to "identity". See senchalabs/connect#414
shakyShane
added a commit
that referenced
this pull request
Jan 31, 2014
Changed accept-encoding header to identity
|
This is on npm now @0.5.4 Thanks again. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The compress module on the node connect server doesn't seem to honor q=0 on gzip, so to make the proxy work with an application I have that uses connect, I had to change the accept-encoding to "identity". See senchalabs/connect#414