Port Change on HTTP redirect, please.
This is still one of the easiest issues to fix. Its a redirect or config change when redirected. I’m not appreciating the price increase - None of the new features matter to me.
Will you take a look if I buy lifetime?
I guess we’re not seeing a lot of reports here which keeps this behind other items with regard to priority.
Can you maybe describe the use case here? What are you hoping to achieve and what exactly is not working?
If there’s something here other people could potentially use it would help us justify committing some time to looking into this.
The usecase is NATPMP, or port forwarding through randomized ports. Its common with VPN and some ISPs. CGNAT is commonplace now, so to unblock port forwarding people seek it thru VPN - its simply the cheapest option, also compared to buying IPv4 you always get VPN annually cheaper and the bandwidth is unlimited.
Since bandwidth is expensive you can’t simply host a reverse proxy that connects directly, you would use up bandwidth in no time. Therefore then reverse proxy has to be redirecting to the randomized port directly on the host.
Maybe the title is not that good, simply Dynamic Port Address would be better.
I guess that makes some sense. We’ll see if we can find some time to look into this. Thanks.
1 Like
I’ll buy a lifetime license this time if this happens. I assume this is quite easy unless there is serious framework limitations preventing it. I assume its simply the URL:Port not updated per redirect, so after authentication it still uses the first request addr.