Skip to content
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

Using an invalid version as a target Quarkus version returns 204 #183

Closed
gastaldi opened this issue Mar 31, 2023 · 0 comments · Fixed by #184
Closed

Using an invalid version as a target Quarkus version returns 204 #183

gastaldi opened this issue Mar 31, 2023 · 0 comments · Fixed by #184
Assignees

Comments

@gastaldi
Copy link
Collaborator

gastaldi commented Mar 31, 2023

The URL is OK. It is using 999-SNAPSHOT as a target Quarkus version. @gastaldi this looks like a registry issue, could you have a look, please?
https://registry.quarkus.io/maven/io/quarkus/registry/quarkus-platforms/1.0-SNAPSHOT/quarkus-platforms-1.0-SNAPSHOT-999-SNAPSHOT.json results in an empty file, as well as the sha1 checksum for it. It should simply return 404 in case the version isn't recognized.

Originally posted by @aloubyansky in quarkusio/quarkus#32266 (comment)

@gastaldi gastaldi self-assigned this Mar 31, 2023
gastaldi added a commit that referenced this issue Mar 31, 2023
- Update status codes for invalid requests
- Remove test for inexistent platforms
- Update test for platforms
- Require all version numbers to be larger than 0 for validation
- Fixes #183

[src/test/java/io/quarkus/registry/app/services/MavenResourceTest.java]
- Change return status code from `400` to `404` for requests with invalid version
- Change return status code from `400` to `404` for requests with invalid snapshot version
- Change return status code from `400` to `404` for requests with invalid version in sha1 file
- Change return status code from `400` to `404` for requests with invalid snapshot version in sha1 file
- Remove test for inexistent platforms
- Update test for
[src/main/java/io/quarkus/registry/app/maven/PlatformsContentProvider.java]
- Change the response status from `NO_CONTENT` to `NOT_FOUND` when no platforms are found
[src/main/java/io/quarkus/registry/app/util/Version.java]
- Require major, minor, and incremental versions to be larger than 0 for validation
gastaldi added a commit that referenced this issue Mar 31, 2023
- Update status codes for invalid requests
- Remove test for inexistent platforms
- Update test for platforms
- Require all version numbers to be larger than 0 for validation
- Fixes #183

[src/test/java/io/quarkus/registry/app/services/MavenResourceTest.java]
- Change return status code from `400` to `404` for requests with invalid version
- Change return status code from `400` to `404` for requests with invalid snapshot version
- Change return status code from `400` to `404` for requests with invalid version in sha1 file
- Change return status code from `400` to `404` for requests with invalid snapshot version in sha1 file
- Remove test for inexistent platforms
- Update test for
[src/main/java/io/quarkus/registry/app/maven/PlatformsContentProvider.java]
- Change the response status from `NO_CONTENT` to `NOT_FOUND` when no platforms are found
[src/main/java/io/quarkus/registry/app/util/Version.java]
- Require major, minor, and incremental versions to be larger than 0 for validation
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant