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.

Sign up for GitHub

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

Jump to bottom

Unhandled Exception when DIDMeta endpoint does not find DID #313

Closed
ThePhisch opened this issue Aug 30, 2023 · 0 comments · Fixed by #459
Closed

Unhandled Exception when DIDMeta endpoint does not find DID #313

ThePhisch opened this issue Aug 30, 2023 · 0 comments · Fixed by #459
Assignees
@maany
Labels
bug Something isn't working
Milestone
35.2.0

Comments

@ThePhisch
Copy link
Contributor

Description

The output of the DIDMeta endpoint is not always a DIDMetaViewModel. Some faulty requests can return a non-JSON object (apparently an HTML page), when instead an errorviewmodel is expected.

Steps to reproduce

  • go to /api/didmeta?scope=x&name=y for x:y not a valid DID
  • the response is not a ViewModel in JSON format but an HTML page!

Rucio WebUI Version

No response

Additional Information

No response
@ThePhisch ThePhisch added the bug Something isn't working label Aug 30, 2023
MytsV added a commit to MytsV/webui that referenced this issue Aug 15, 2024
@MytsV
Gateway error handling: add a handler for 404 status code and fix the…
c103314 
… 400 status code message

Fixes rucio#313
@MytsV MytsV mentioned this issue Aug 15, 2024
Merged
@maany maany added this to the 35.2.0 milestone Aug 15, 2024
@maany maany closed this as completed in 9841853 Aug 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@maany maany

Labels
bug Something isn't working
Projects
None yet
Milestone
35.2.0
Development

Successfully merging a pull request may close this issue.

Bug 313. Unhandled response status codes in BaseEndpoint MytsV/webui
2 participants
@maany @ThePhisch