APIGEE returns 200 despite the target server returning 400

[#1]

Hello All,

We are seeing a case where, on the target server, we are specifically setting the response status code to 400, we also see in the trace that APIGEE shows 400, but when checking in postman we see 200 as response status code.

Are we doing any thing wrong, or should we add any other specfic rule to correct this?

[ssvaidyanathan]

@Santosh Kumar U P

Are you sure you are tracing the call you made in your POSTMAN ?

Are you hitting an external API, if yes, can you share the proxy bundle ?

[#3]

Hello Sai,

I have double checked. I am hitting correct proxy. Unfortunately, it is an on prem APIGEE and not accessible out side.

[ssvaidyanathan]

HI @Santosh Kumar U P - Where are you based out of ? I am happy to get into a meeting with you to check this behavior.

[#5]

Sure, please share your email id. We can get onto meeting 🙂

[ssvaidyanathan]

@Santosh Kumar U P

Sent you an email to your gmail id that is used in our community.

[ssvaidyanathan]

All good here... Had a meeting with @Santosh Kumar U P. Apigee works as expected. The downstream DMZ is converting the 400 to a 200.

Santhosh - Please accept this post if its resolved