Proxyman alters the header case

[kotori2]

Description

Proxyman will change all header to lower case, even if HTTP/1.1 is used

Steps to Reproduce

1. Visit any website that supports only HTTP/1.1, with proxyman configured

2. Check for the raw response tab

Current Behavior

All headers are in lower case. However if you are accessing the same URL with cURL and without proxy, you will see the response is actually in Camel Case.

It causes some applications (in my case, Dell RACADM) that search for case-sensitive headers to fail.

Some logs from that app if you are curious:

12037140 DEBUG: sslsocket.c [587]: Calling HttpSendRequest
12037500 DEBUG: sslsocket.c [597]: HttpSendRequest return code = 1
12037546 DEBUG: xmlhttp.c [2263]: Reading response...
12037546 DEBUG: xmlhttp.c [1766]: Reading HTTP headers...
12037546 DEBUG: xmlhttp.c [1776]: HTTP Response Headers:
HTTP/1.1 200 OK
strict-transport-security: max-age=63072000
vary: Accept-Encoding
keep-alive: timeout=60, max=199
x-frame-options: SAMEORIGIN
content-type: text/xml
date: Mon, 28 Apr 2025 11:39:21 GMT
etag: 1711716376
connection: close
accept-ranges: bytes
transfer-encoding: chunked


12037546 DEBUG: xmlhttp.c [1821]: Searching for Content-Length field...
12037562 DEBUG: xmlhttp.c [1828]: Searching for Content-length field because Content-Length was not found

Expected Behavior

Proxyman should not alter the response for HTTP/1.1. I know you have to reassemble that for HTTP/2, but please leave HTTP/1.1 alone.

Environment

• App version: 2.23.0
• Windows/Linux version: 26100.3624

[kics223w1]

Hi @kotori2,

We are aware of this behavior, but we haven't made any updates related to it yet.
Let me discuss it with @NghiaTranUIT, and we will keep you updated.

Thank you!

[kotori2]

Thanks @kics223w1 !

[NghiaTranUIT]

@kotori2 it's a bug, and we're working on the fix 👍