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
Relative locations are allowed when the status code is a redirect. The location url should resolve to the effective request URI: https://tools.ietf.org/html/rfc7230#section-5.5
The issue:
Request http://example.com/redirect Response { ... statusCode : 303, headers : { Location: "/redirected" ... } }
http://example.com/redirect
{ ... statusCode : 303, headers : { Location: "/redirected" ... } }
Expected: The new request url should be http://example.com/redirected
http://example.com/redirected
Actual: The new request url is /redirected
/redirected
The text was updated successfully, but these errors were encountered:
Successfully merging a pull request may close this issue.
Relative locations are allowed when the status code is a redirect. The location url should resolve to the effective request URI: https://tools.ietf.org/html/rfc7230#section-5.5
The issue:
Request
http://example.com/redirectResponse
{ ... statusCode : 303, headers : { Location: "/redirected" ... } }Expected:
The new request url should be
http://example.com/redirectedActual:
The new request url is
/redirectedThe text was updated successfully, but these errors were encountered: