Conversation
Don't prepend content headers for PHP
|
We just stumbled upon this header bug, trying to set This PR needs some clean-up, though, as the changes from commit 65d4a10 are no longer needed (already implemented with #209). @themizzi can you please update this PR or create a new PR with only commit 7742b0a (Content-Header Fix)? |
This reverts commit 65d4a10.
|
@elkangaroo I have reverted the unnecessary commit. |
|
Awesome, thx @themizzi 👍 |
|
See #218. It also contains tests and some improvements. |
|
ping @OskarStark |
|
For me, a good PR could be this one with headers.feature. #218 does two other things could be discussed separetly. |
|
sounds good, unless you don't get any feedback I could submit a new one with this fix and the feature |
|
Now #218 is ok for me. |
|
@sanpii can you please merge and release this? all checks are green now |
|
#218 merged. |
|
Yay, thank you @sanpii 🎉 |
|
@OskarStark I would like fix travis build before. |
|
any news here? Is this PR (which is not release yet) maybe related to the travis problem? |
Two things: 1) it stores the client so headers are lost between calls to setHttpHeaders. 2) setHttpHeaders handles Content headers appropriately.