Daniele Orru'
Daniele Orru'
EDIT: You're right there is some work to do to make it happens.
Not for me, I see `https://mywebsite.local.com` in `HTTP_HOST`
No difference, I still see the 'wrong' header. But now that you're telling me that the tool should already handle it. I suppose it has something to do with my...
Looks like my application-level code sees the 'wrong' header with ngrok as well (and that's fine as long as I get redirected to the correct host), so I suppose the...
I did not know http://127.0.0.1:4040, so that's the result: Request: ``` GET / Host | myservice.local.it X-Original-Host | bbd708a5e84c.ngrok.io X-Forwarded-For | my-ip-address (redacted) ``` Response: ``` 302 Found Location |...
Yes, they look the same ``` GET / Host myservice.local.it:443 x-original-host xudu45wyce.sharedwithexpose.com x-forwarded-for my-ip-address ``` Response ``` 302 Found Location https://myservice.local.it/login ``` but the actual curl with expose says ```...
Just tested, and it did not solve my problem. Just to clarify: I could easily fiddle with traefik (or nginx) and headers to fool my web server and make it...
The key is to replace `Host` with `X-Original-Host` in your web server. Traefik does not allow dynamic header rewrite (I think it's in the works), but you can still hardcode...
I'm not sure it's good to close the issue here. While we can actually fiddle with webserver\proxy parameters to get it right, ngrok doesn't need to do it in order...
Yes, it's still happening in 1.5.1. I'll try to create a mini-application in the next week or two, so you can actually reproduce it.