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

Bug 313. Unhandled response status codes in BaseEndpoint #459

Merged
merged 3 commits into from
Aug 15, 2024
Merged

Bug 313. Unhandled response status codes in BaseEndpoint #459

merged 3 commits into from
Aug 15, 2024

Commits on Aug 15, 2024

  1. Gateway error handling: add a handler for 404 status code and fix the… 

    … 400 status code message

Fixes rucio#313
    @MytsV
    MytsV committed Aug 15, 2024
    Configuration menu
    Copy the full SHA
    c103314 View commit details
    Browse the repository at this point in the history

  2. Gateway error handling: produce unknown error by default 

    This makes all the other possible status codes cause the API page to return a valid JSON instead of HTML that may break the app
    @MytsV
    MytsV committed Aug 15, 2024
    Configuration menu
    Copy the full SHA
    a77bd43 View commit details
    Browse the repository at this point in the history

  3. Gateway error handling: decompose the message handling and stringify … 

    …it for display
    @MytsV
    MytsV committed Aug 15, 2024
    Configuration menu
    Copy the full SHA
    cdae75c View commit details
    Browse the repository at this point in the history