[GH-ISSUE #391] [BUG] Invalid network connection when log-in with DeepL app #388

New issue

Open

opened 2026-03-03 19:18:07 +03:00 by kerem · 1 comment

kerem commented

2026-03-03 19:18:07 +03:00

Owner

Originally created by @NghiaTranUIT on GitHub (Feb 4, 2020).
Original GitHub issue: https://github.com/ProxymanApp/Proxyman/issues/391

Originally assigned to: @NghiaTranUIT on GitHub.

🐶 Brief

For some reasons, we couldn't intercept the Login API from DeepL app. The connection is still active, and the app get Networking error.

Other requests from DeepL app are working well.

👑 Criteria

Investigate and fix it

Originally created by @NghiaTranUIT on GitHub (Feb 4, 2020). Original GitHub issue: https://github.com/ProxymanApp/Proxyman/issues/391 Originally assigned to: @NghiaTranUIT on GitHub. ## 🐶 Brief For some reasons, we couldn't intercept the Login API from DeepL app. The connection is still active, and the app get Networking error. Other requests from DeepL app are working well. ## 👑 Criteria - [ ] Investigate and fix it

kerem added the

bug

✅ Done

labels

2026-03-03 19:18:07 +03:00

kerem commented

2026-03-03 19:18:08 +03:00

Author

Owner

@NghiaTranUIT commented on GitHub (Feb 4, 2020):

It turns out that the HTTP Request Message from DeepL is incorrect format. To particular, one Header is application/json: ContentType, which is mis-order.

As a result, HTTPParser doesn't recognize properly and shot an error.

I would suggest to improve how Proxyman treats the HTTP Message from the client. Instead of throwing the error due to failed invalid format. Proxyman might ignore it and send through the server.

@NghiaTranUIT commented on GitHub (Feb 4, 2020): It turns out that the HTTP Request Message from DeepL is [incorrect format](https://developer.mozilla.org/en-US/docs/Web/HTTP/Messages). To particular, one Header is `application/json: ContentType`, which is mis-order. As a result, HTTPParser doesn't recognize properly and shot an error. I would suggest to improve how Proxyman treats the HTTP Message from the client. Instead of throwing the error due to failed invalid format. Proxyman might ignore it and send through the server.