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
Hi! I've faced with the following issue:
Here is an example I'm trying:
- request: method: [GET] redirect_uri: ^/v\d/identity/authorize query: redirect_uri: "https://(.*)/app.*" response: headers: location: https://<% query.redirect_uri.1 %>/auth status: 302
Unfortunately, doing mentioned request I don't get "location" header in the response at all. Seems like exception happens on backend side.
Looking into the code, only DefaultResponseHandlingStrategy supports tokenized "location" header.
I can fix it. If you don't mind :)
The text was updated successfully, but these errors were encountered:
@dimadl thank you. Will review your PR soon
Sorry, something went wrong.
Merge pull request #91 from dimadl/tokenized_location_header
c6c8936
Fixes issue #90 - Added ability to use tokenized "Location" header in 3xx responses
No branches or pull requests
Hi!
I've faced with the following issue:
Here is an example I'm trying:
Unfortunately, doing mentioned request I don't get "location" header in the response at all. Seems like exception happens on backend side.
Looking into the code, only DefaultResponseHandlingStrategy supports tokenized "location" header.
I can fix it. If you don't mind :)
The text was updated successfully, but these errors were encountered: