Is there a way to handle the error code "protocol.http.InvalidPath" more gracefully ?

We have noticed that when we add certain special characters in url paths like this:

https://<host alias>/v1/some[]ids/resource

Apigee is unable to route this to our API Proxies and instead returns 400 Bad Request with the below error message to the clients.

{"fault":{"faultstring":"Invalid path GET \/some[]ids\/resource HTTP\/1.1","detail":{"errorcode":"protocol.http.InvalidPath"}}}

We would like to have these kind of requests routed to a Proxy named "InvalidRequestsAPIProxy", but these requests are not hitting this proxy.

Is there some way we can handle these kind of requests more gracefully ?

0 2 1,839

2 REPLIES 2