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
🛑 When retry is enabled, all exceptions return 404
Problem Phenomenon
I created an API gateway, turned on the retry policy, requested an action for a nonexistent service, and found that the error message returned was 404 instead of the service is not registered.
Failure Information
I tried to trace the code, and found that an external request will first enter the rest handler, then parse the route, and call the real request. When the real request fails, rest will also retry, but in line 64 of retrie.js, it will use the current context to retry, at this time the url has changed and there is no route information. Therefore, null is returned
I understand this is to prevent the request of rest in the same class to be repeated, but how to return the correct error rather than 404
The text was updated successfully, but these errors were encountered:
🛑 When retry is enabled, all exceptions return 404
Problem Phenomenon
I created an API gateway, turned on the retry policy, requested an action for a nonexistent service, and found that the error message returned was 404 instead of the service is not registered.
Failure Information
I tried to trace the code, and found that an external request will first enter the rest handler, then parse the route, and call the real request. When the real request fails, rest will also retry, but in line 64 of retrie.js, it will use the current context to retry, at this time the url has changed and there is no route information. Therefore, null is returned
I understand this is to prevent the request of rest in the same class to be repeated, but how to return the correct error rather than 404
The text was updated successfully, but these errors were encountered: