[GH-ISSUE #501] Proxyman alters the header case #500

New issue

Open

opened 2026-03-03 19:50:59 +03:00 by kerem · 3 comments

kerem commented 2026-03-03 19:50:59 +03:00

Owner

Copy link

Originally created by @kotori2 on GitHub (Apr 28, 2025).
Original GitHub issue: https://github.com/ProxymanApp/proxyman-windows-linux/issues/501

Originally assigned to: @kics223w1 on GitHub.

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

Originally created by @kotori2 on GitHub (Apr 28, 2025). Original GitHub issue: https://github.com/ProxymanApp/proxyman-windows-linux/issues/501 Originally assigned to: @kics223w1 on GitHub. ## Description Proxyman will change all header to lower case, even if HTTP/1.1 is used ## Steps to Reproduce <!-- Add relevant code and/or a live example --> 1. Visit any website that supports only HTTP/1.1, with proxyman configured 2. Check for the raw response tab ## Current Behavior <!--- What went wrong? --> 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 <!--- What should have happened? --> 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

kerem added the

✅ Done

bug

labels 2026-03-03 19:50:59 +03:00

kerem commented 2026-03-03 19:50:59 +03:00

Author

Owner

Copy link

@kics223w1 commented on GitHub (Apr 28, 2025):

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!

<!-- gh-comment-id:2833916584 --> @kics223w1 commented on GitHub (Apr 28, 2025): 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!

kerem commented 2026-03-03 19:50:59 +03:00

Author

Owner

Copy link

@kotori2 commented on GitHub (Apr 28, 2025):

Thanks @kics223w1 !

<!-- gh-comment-id:2833917185 --> @kotori2 commented on GitHub (Apr 28, 2025): Thanks @kics223w1 !

kerem commented 2026-03-03 19:51:00 +03:00

Author

Owner

Copy link

@NghiaTranUIT commented on GitHub (May 5, 2025):

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

<!-- gh-comment-id:2849763688 --> @NghiaTranUIT commented on GitHub (May 5, 2025): @kotori2 it's a bug, and we're working on the fix 👍

Sign in to join this conversation.

No Branch/Tag specified

Branches Tags

main

feat/new-version

3.12.0

3.11.0

3.10.0

3.4.0

3.5.0

3.6.0

3.7.0

3.8.0

3.9.0

3.3.0

2.25.0

2.24.0

3.2.0

3.0.0

3.1.0

2.26.0

2.27.0

2.23.0

2.22.0

2.21.0

2.20.0

2.19.0

2.18.0

2.17.0

2.16.0

2.15.0

2.14.0

2.13.0

2.12.0

2.11.1

2.11.0

2.10.0

2.9.0

2.8.0

2.7.0

2.6.0

2.5.0

2.4.0

2.3.0

1.9.2

2.0.0

1.9.1

1.8.1

1.9.0

1.8.0

1.7.0

1.6.0

1.5.0

1.4.0

1.3.0

1.2.0

1.1.0

1.0.0

0.10.0

0.9.0

0.8.0

0.6.0

0.5.0

0.4.2

0.4.1

0.4.0

0.3.0

0.1.1

0.2.0

0.1.0

Labels

Clear labels   

Linux

  

bug

  

enhancement

  

enhancement

  

pull-request

Mirrored from GitHub Pull Request

  

question

  

✅ Done

No labels

Linux

bug

enhancement

enhancement

pull-request

question

✅ Done

Milestone

Clear milestone

No items

No milestone

Projects

Clear projects

No items

No project

Assignees

Clear assignees

No assignees

1 participant

Notifications

Subscribe

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

starred/proxyman-windows-linux#500

No description provided.