ProxymanApp / ProxymanApp/Proxyman

Endpoint failing due to port attached to host using Reverse Proxy

Open
#2,412 5 comments 0 reactions 1 assignee View on GitHub

@NghiaTranUIT is already working on this.

Since Jul 12, 2025.

✅ Done bug
Dominant language
No language data
Stars
7k
Forks
237
PR merge metrics
No merged PRs in 30d

Description

Description

I am not sure if this is a bug or not, also curious about your opinion.
We have an endpoint that is not working with Reverse Proxy, because Proxyman sets the Host header as follows:

Host: example.com:443

The endpoint returns an error and only works when the Host is set like this:

Host: example.com

So without the port number behind it.
I am not too familiar with HTTP standards on this, if this is a Proxyman bug or if the endpoint is just too strict (there is no internal error, it is a 500 error returned by the endpoint).

I have the following workaround that fixes it for me:
In scripting tool I have set up the following script on this endpoint, so that the port is not sent:

URL: example.com/*
ANY / Use wildcard / Run Script on: Request

async function onRequest(context, url, request) {
  request.headers["Host"] = "example.com";
  return request;
}
  • App version: e.g Proxyman 5.22.0, but I don't think the version matters
  • macOS version: e.g macOS Monterey

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.