We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Currently, weave proxies everything, so you think you're talking to localhost:1234 but you're actually talking to foo.com.
An option could be added to tell a route to send back redirect headers rather than internally proxy the request.
Weave could then be used to forward you from some url you've constructed to the real deatinstion(s).
Is this actually useful though?
The text was updated successfully, but these errors were encountered:
Possibly a more useful feature down the same line is having weave handle redirects itself rather than giving them back to the user.
Sorry, something went wrong.
No branches or pull requests
Currently, weave proxies everything, so you think you're talking to localhost:1234 but you're actually talking to foo.com.
An option could be added to tell a route to send back redirect headers rather than internally proxy the request.
Weave could then be used to forward you from some url you've constructed to the real deatinstion(s).
Is this actually useful though?
The text was updated successfully, but these errors were encountered: