-
Notifications
You must be signed in to change notification settings - Fork 530
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Handlers that handle proxy specific things, such as resolving a full url for outside use, or knowing if https #157
Comments
Yes, the auto redirects are to solve the issues that are common, for the common headers that load balancers / proxies use. Currently, everyone has to learn how to do that themselves or do some hacky way (config for what my root path of my app is, parse the URL, shove in the new part of the URL, redirect) which breaks down when you do more virtual hosts and more complicated scenarios. For example, one framework I see does about this much work which is pretty standard that I would prefer everyone not try to figure out on their own:
That is the minimal redirect, and makes assumptions that are likely correct for http https protocol URL's. |
And if your deployment has a root context (such as servlet base path) that has to be taken into account, etc. |
@apartida if you could translate that to Java and submit a PR then it would help getting this into master as something like |
Need some help with that? |
Here's a non-working prototype: slayful@8cb7b74 |
This has been fixed with: 136ff03 and other improvements. |
A lot of people write common code to deal with things like:
"am I on secure connection?" (have to look at proxy / load balancer headers to know)
"I need a fully qualified link to one of my routes for an outside resource to use" (for example, giving an oauth service the callback URL and making it correct for the given server, protocol, host, etc)
The text was updated successfully, but these errors were encountered: