[GH-ISSUE #3919] Reponse header sets wrong location

gitea-mirror commented

2026-05-05 14:00:53 -06:00

Owner

Copy link

Originally created by @cedricbieder on GitHub (Jan 8, 2024).
Original GitHub issue: https://github.com/fatedier/frp/issues/3919

Bug Description

I am using a frp-http tunnel to get access to a webapplication. I can also reach the login screen of this app with subdomain.mydomain.com:443. If I log in, the authentication response returns in the header a new location with subdomain.mydomain.com:82 and the browser redirects to this port. I always have to remove this port again to work normal on the 443 tunnel. Is there a parameter which I can set to manipulate this response location?

frpc Version

0.53

frps Version

0.53

System Architecture

linux/amd64

Configurations

[16]
type=https
local_ip=127.0.0.1
local_port=82
subdomain=subdomain
#host_header_rewrite=subdomain.domain.com
[common]
server_addr=server.domain.com
server_port=443
authentication_method=token
token=my_token
log_level=trace
user=my_user
tls_enable=true

Logs

No response

Steps to reproduce

...

Affected area

Docs
Installation
Performance and Scalability
Security
User Experience
Test and Release
Developer Infrastructure
Client Plugin
Server Plugin
Extensions
Others

Originally created by @cedricbieder on GitHub (Jan 8, 2024). Original GitHub issue: https://github.com/fatedier/frp/issues/3919 ### Bug Description I am using a frp-http tunnel to get access to a webapplication. I can also reach the login screen of this app with subdomain.mydomain.com:443. If I log in, the authentication response returns in the header a new location with subdomain.mydomain.com:82 and the browser redirects to this port. I always have to remove this port again to work normal on the 443 tunnel. Is there a parameter which I can set to manipulate this response location? ### frpc Version 0.53 ### frps Version 0.53 ### System Architecture linux/amd64 ### Configurations [16] type=https local_ip=127.0.0.1 local_port=82 subdomain=subdomain #host_header_rewrite=subdomain.domain.com [common] server_addr=server.domain.com server_port=443 authentication_method=token token=my_token log_level=trace user=my_user tls_enable=true ### Logs _No response_ ### Steps to reproduce 1. 2. 3. ... ### Affected area - [ ] Docs - [ ] Installation - [X] Performance and Scalability - [ ] Security - [X] User Experience - [ ] Test and Release - [ ] Developer Infrastructure - [ ] Client Plugin - [ ] Server Plugin - [ ] Extensions - [ ] Others

gitea-mirror

2026-05-05 14:00:53 -06:00

closed this issue
added the
lifecycle/stale
label

gitea-mirror commented

2026-05-05 14:00:56 -06:00

Author

Owner

Copy link

@fatedier commented on GitHub (Jan 9, 2024):

You can modify it in your own app.

@fatedier commented on GitHub (Jan 9, 2024): You can modify it in your own app.

gitea-mirror commented

2026-05-05 14:00:57 -06:00

Author

Owner

Copy link

@github-actions[bot] commented on GitHub (Jan 31, 2024):

Issues go stale after 21d of inactivity. Stale issues rot after an additional 7d of inactivity and eventually close.

@github-actions[bot] commented on GitHub (Jan 31, 2024): Issues go stale after 21d of inactivity. Stale issues rot after an additional 7d of inactivity and eventually close.

gitea-mirror referenced this issue

2026-05-05 14:46:43 -06:00

[PR #3110] [CLOSED] Cr 14344 #4682

No Branch/Tag specified