-
-
Notifications
You must be signed in to change notification settings - Fork 598
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
ERROR 400 Ambiguous URI path separator #4238
Comments
Appears to be caused by a behavior change in Jetty: jetty/jetty.project#12162 |
Thanks for quick feedback @nscuro . |
There seem to be ways to make it behave like before, I'll ensure we ship a fix with the next bugfix release. |
…ment Due to a change in Jetty 12 and the Servlet API 6, it is no longer valid to pass URL-encoded values as path parameters. This is problematic for REST APIs such as Dependency-Track's, where this behavior causes endpoints to be unusable with certain parameters: DependencyTrack/dependency-track#4238 Restore the legacy behavior of Jetty 9 for now. For the next major version bump of Alpine, this can be reversed to follow Servlet API 6 more strictly.
…ment Due to a change in Jetty 12 and the Servlet API 6, it is no longer valid to pass URL-encoded values as path parameters. This is problematic for REST APIs such as Dependency-Track's, where this behavior causes endpoints to be unusable with certain parameters: DependencyTrack/dependency-track#4238 Restore the legacy behavior of Jetty 9 for now. For the next major version bump of Alpine, this can be reversed to follow Servlet API 6 more strictly. Signed-off-by: nscuro <nscuro@protonmail.com>
The *tagged projects*, *tagged policies*, and *tagged alerts* dialogs would show an empty list for tags that contain special characters such as `/`. This was caused by both DependencyTrack/dependency-track#4238, and tag names not being URI-encoded prior to using them as path parameters. Signed-off-by: nscuro <nscuro@protonmail.com>
The *tagged projects*, *tagged policies*, and *tagged alerts* dialogs would show an empty list for tags that contain special characters such as `/`. This was caused by both DependencyTrack/dependency-track#4238, and tag names not being URI-encoded prior to using them as path parameters. Signed-off-by: nscuro <nscuro@protonmail.com>
We’re experiencing the same issue and are looking forward to the fix. 🚀 |
Just waiting for an Alpine release so we can pull the fix in. Will release v4.12.1 immediately afterwards, it's ready otherwise. |
Fixes DependencyTrack#4238 Signed-off-by: nscuro <nscuro@protonmail.com>
Fixes DependencyTrack#4238 Signed-off-by: nscuro <nscuro@protonmail.com>
I have a self hosted dependencytrack instance where I call the endpoint
|
@Yingrjimsch That is a different issue. |
No, if I request a badge through the project ID there is no problem |
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Current Behavior
In my test environment, I set up a Docker Compose file with Dependency-Track version 4.12.0.
In production, we are currently running version 4.11.7, and the endpoint described below works without issues, both in production and the test environment.
We make extensive use of tags, especially prior to the introduction of the new tag feature, so it's fair to say that we overuse the /project/tag endpoint.
In the latest version, however, I'm unable to query tags because I receive a ERROR 400 Ambiguous URI path separator when a request query includes a tag that contains a forward slash /.
Were there any changes in the latest release regarding the handling of UTF-8 encoded query strings? Specifically, is there now any support for queries with slashes in tags?
Steps to Reproduce
For example:
Expected Behavior
Return all projects with that tag.
Dependency-Track Version
4.12.0
Dependency-Track Distribution
Container Image
Database Server
PostgreSQL
Database Server Version
15
Browser
Other
Checklist
The text was updated successfully, but these errors were encountered: