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

access-api: when store/upload proxy encounters an HTTPError, the proxied invocation should get an error result, not a HandlerExecutionError #365

Open
gobengo opened this issue Jan 18, 2023 · 0 comments
Open

access-api: when store/upload proxy encounters an HTTPError, the proxied invocation should get an error result, not a HandlerExecutionError #365

gobengo opened this issue Jan 18, 2023 · 0 comments
Assignees
@gobengo

Comments

@gobengo
Copy link
Contributor

gobengo commented Jan 18, 2023 •
edited
Loading

Motivation:

What

  • it's not that uncommon for a proxy to have its upstream go down or otherwise error. When this happens, we should have the proxy service return a well-defined error message similar to HTTP 502 Bad Gateway
@gobengo gobengo self-assigned this Jan 18, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@gobengo gobengo

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@gobengo