Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

jersey-netty-connector - Relative path returned in Location header is used as is #5438

Closed
sxsubram opened this issue Oct 13, 2023 · 0 comments · Fixed by #5442
Closed

jersey-netty-connector - Relative path returned in Location header is used as is #5438

sxsubram opened this issue Oct 13, 2023 · 0 comments · Fixed by #5442

Comments

@sxsubram
Copy link

https://www.rfc-editor.org/rfc/rfc7231#section-7.1.2
Location = URI-reference
The field value consists of a single URI-reference. When it has the form of a relative reference ([RFC3986], Section 4.2), the final value is computed by resolving it against the effective request URI ([RFC3986], Section 5).

In v2.40 relative URI is being used as is and resulting in errors.
_An error occurred while invoking the REST endpoint.[[org.glassfish.jersey.netty.connector.internal.RedirectException: "Error determining redirect location:

@sxsubram sxsubram changed the title Relative path returned in Location header id used as is Relative path returned in Location header is used as is Oct 13, 2023
@sxsubram sxsubram changed the title Relative path returned in Location header is used as is jersey-netty-connector - Relative path returned in Location header is used as is Oct 17, 2023
@jansupol jansupol linked a pull request Oct 18, 2023 that will close this issue
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants