You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If the request.Attempt failed (i.e. upstream is unavailable), there is no response, and no way for the middleware to communicate back to the client.
It would be nice to be able to return an error page other than {"error":"Bad Gateway"}, but we can't without access to a Response or something that can write to the http.ResponseWriter.
The text was updated successfully, but these errors were encountered:
If the request.Attempt failed (i.e. upstream is unavailable), there is no response, and no way for the middleware to communicate back to the client.
It would be nice to be able to return an error page other than
{"error":"Bad Gateway"}
, but we can't without access to a Response or something that can write to the http.ResponseWriter.The text was updated successfully, but these errors were encountered: