[TIMOB-27701] iOS: Changing request-header in HTTPClient re-appends the new header value
GitHub Issue | n/a |
---|---|
Type | Bug |
Priority | Critical |
Status | Open |
Resolution | Unresolved |
Affected Version/s | n/a |
Fix Version/s | n/a |
Components | iOS |
Labels | engTriage, httpclient, ios, requestHeader |
Reporter | Hans Knöchel |
Assignee | Unknown |
Created | 2019-12-30T12:01:44.000+0000 |
Updated | 2020-09-23T08:20:03.000+0000 |
Description
We noticed that if we re-run a request with new request headers (e.g. with a new access token), the new header value is just appended to the old header instead of overwriting the the value.
For example, if my initial request has
request.setRequestHeader('Test', 'myValue');
and I overwrite it with request.setRequestHeader('Test', 'myNewValue');
, the actual header sent to the server is 'Test: myValue, myNewValue'
.
This is very critical for production grade apps! I would fix it myself, but unfortunately APSHTTPClient (the library used internally) is closed source.
Any update on this?