[TIMOB-28060] Ti.API: Parity issue in HTTPClient response headers
| GitHub Issue | n/a |
|---|---|
| Type | Bug |
| Priority | None |
| Status | Closed |
| Resolution | Duplicate |
| Resolution Date | 2020-08-13T17:02:44.000+0000 |
| Affected Version/s | n/a |
| Fix Version/s | n/a |
| Components | Android, iOS |
| Labels | n/a |
| Reporter | Hans Knöchel |
| Assignee | Gary Mathews |
| Created | 2020-07-31T08:17:29.000+0000 |
| Updated | 2020-08-13T17:03:32.000+0000 |
Description
There is a major parity issue when working with response headers in Titanium. On iOS, there is the [
responseHeaders](http://docs.appcelerator.com/platform/latest/#!/api/Titanium.Network.HTTPClient-property-responseHeaders) property that returns a proper dictionary of all response headers. On Android, there is the [allResponseHeaders](http://docs.appcelerator.com/platform/latest/#!/api/Titanium.Network.HTTPClient-property-allResponseHeaders) property that returns all response headers combined as a string. That one should be deprecated and move to the more commonly used dictionary pattern (like other libraries do).
Closing as duplicate of [TIMOB-24983]