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 path_translation: CONSTANT_ADDRESS is used at the endpoint level and the address includes a resource path the ESP does not forward the request to the target backend address.
With the below configuration the requests are forwarded (the target backend returns 404 because there is nothing at root path):
ESP returns a 404 and does not attempt to forward the request to the target backend when target address included a resource
Tested with 2.47.0 and 2.50.0
Please advise if this is a bug or me doing something wrong
The text was updated successfully, but these errors were encountered:
karolpivo
changed the title
Request are not forwarded to the target if "address" URL includes a resource path
Requests are not forwarded to the target if "address" URL includes a resource path
Aug 2, 2024
When
path_translation: CONSTANT_ADDRESS
is used at the endpoint level and theaddress
includes a resource path the ESP does not forward the request to the target backend address.With the below configuration the requests are forwarded (the target backend returns 404 because there is nothing at root path):
Screenshot below shows the GCP logs. The behavior is as expected
With the below configuration the Cloud Endpoint / ESP simply returns a 404 and does not attempt to forward to the target
Screenshot below shows the GCP logs.
Expected behavior:
ESP forwards the request to
address: https://ourendpoint-2jxxxxdi7a-lm.a.run.app/healthz
whenpath_translation: CONSTANT_ADDRESS
is setThis is how it should work according to documentation https://cloud.google.com/endpoints/docs/openapi/openapi-extensions#understanding_path_translation
Actual behavior
ESP returns a 404 and does not attempt to forward the request to the target backend when target address included a resource
Tested with 2.47.0 and 2.50.0
Please advise if this is a bug or me doing something wrong
The text was updated successfully, but these errors were encountered: