On 18-Sep-12 11:41, Johannes Pfau wrote:
Am Mon, 17 Sep 2012 22:35:39 +0200
schrieb "Jonathan M Davis" <[email protected]>:
On Monday, September 17, 2012 20:59:05 Johannes Pfau wrote:
addRequestHeader is quite dumb. It simply appends the header to a
list. So by just calling it again you would actually send 2
Content-Type headers.
So, you're suggesting to send 2 content headers? That can't be good.
It might work, but I'm pretty darn sure that it's against the HTTP
spec to do so. You're only supposed to have duplicate headers when
they're values are a list, and they can be concatenated into a single
header.
- Jonathan M Davis
No I'm not suggesting it, but that is what's being done if you call
addRequestHeader twice. Dmitry said addRequestHeader didn't work for
him and I wanted to explain that calling addRequestHeader again does
not overwrite the first value.
Yeah, that's the case. Thanks Johannes, I'll use your workaround for now.
Still I believe it worths an enhancement request. Setting content type
is a basic task.
--
Dmitry Olshansky
