no longer sets Content-Length header in BackLogin #12
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.
My attempts at opening the Roundcube application ended up as request timeouts. After looking up the issue, I stumbled upon this:
https://stackoverflow.com/questions/24779634/php-curl-timeout-in-redirections
I think we can assume that, for whatever reasons,
strlen($postData)wasn't returning the proper value for Content-Length, resulting in Roundcube never responding to a request that didn't consist of as many bytes as expected.The solution to this is actually pretty simple: if unspecified, php-curl will set the Content-Length header on its own. It's probably best not to interfere, and that's exactly the intent of this PR.