API Proxy and HTTP Header validation

sunin_shah
Participant II

I am validation the content-type header within my proxy. However in some situation, when I send an incorrect 'charset' parameter in the content-type header, it seems to send the apigee platform into a spin. So for example if I set the Content-Type to 'application/x-www-form-urlencoded;charset=xxx-8', then my proxy flow never gets executed. See following screen dump of proxy executions and the top one still 'thinking' due to incorrect Content-Type header. Any ideas on whether it is possible to protect against this type of invalid data being sent to our proxies?

content-type-issue.png

1 0 1,147
0 REPLIES 0