-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
HttpURI.toURI() sets userInfo to null #11465
Labels
Bug
For general bugs on Jetty side
Comments
Yeah, I see no reason not to pass those over now. If fact, considering that all URI constructors end up creating and then parsing the string version of the URI, we might as well just pass in the string version anyway. See PR #11468 |
gregw
added a commit
that referenced
this issue
Feb 29, 2024
* HttpURI toURI passes all info Fix #11465 and #7750 HttpURI.toURI user and fragment are retained. Use to URI(String) constructor, as all URI constructors will parse the URI anyway. * HttpURI toURI passes all info Fix #11465 and #7750 HttpURI.toURI user and fragment are retained. Use to URI(String) constructor, as all URI constructors will parse the URI anyway.
github-project-automation
bot
moved this from 🏗 In progress
to ✅ Done
in Jetty 12.0.7 - FROZEN
Feb 29, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Jetty version(s)
12.0.6
Jetty Environment
core
Description
Similar to #7750 I am wondering why
toURI()
forcesuserInfo
tonull
when other methods use it as-is.I am expecting
toURI()
to return all the available information.The text was updated successfully, but these errors were encountered: