Always send Content-Length header. Fixes compatibility issues with el… #289
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
|
Manual check verifies that you have signed the CLA, but would you mind getting the tests passing? |
|
Hi, at first I'll have to get the tests running ;-) But yes, I'll give it a go soon-ish (y) |
|
Here ya go! |
|
Awesome :) thanks! |
spalger
added a commit
that referenced
this pull request
Nov 30, 2015
Always send Content-Length header. Fixes compatibility issues with el…
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.
…asticsearch behind nginx.
See sous-chefs/elasticsearch#38 or http://serverfault.com/questions/164220/is-there-a-way-to-avoid-nginx-411-content-length-required-errors