ProxymanApp / ProxymanApp/Proxyman
Unusual behaviour for response headers keys registry
@NghiaTranUIT is already working on this.
Since Jan 14, 2020.
- Dominant language
- No language data
- Stars
- 7k
- Forks
- 237
- PR merge metrics
- No merged PRs in 30d
Description
Proxyman version: 1.13.1
macOS Version: 10.15.2
Hey! Thanks a lot for an amazing tool, but I have a question...
I'm developing iOS application with Alamofire (most common 3-party network library) and using http-headers from our internal server responses. Alamofire provides case-insensitive keys for all headers (they are all lower-cased).
But there is a problem when I use Proxyman: after getting response that pass through Proxyman I have a case like X-Custom-Header. When I toggle-off proxy I get x-custom-header as I expect
Is any way to change or understand this behaviour?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.