Hi Jeff,
I'm assuming the 400 Bad Request Error is coming from your backend server? I don't have a v2018 environment to look at since it is out of support, but I've typically seen this type of issue due the the invoke 2.0.0 policy using chunked uploads by default and the backend doesn't process it well. I know there is an option in the invoke policy in v10 for enabling or disabling chunked uploads, so hopefully it is there in v2018 as well. If the error is not coming from your backend but by something in your API assembly, I would suspect a parse policy that would be failing, perhaps a payload is larger than the default parser limits. If you have access to the DataPower appliance, I'd enable debug logging and run one transaction and gather the default logs. You can follow those through the processing of the API to see where the failure is coming from.
Best Regards,
Steve Linn
------------------------------
Steve Linn
Senior Consulting I/T Specialist
IBM
------------------------------
Original Message:
Sent: Thu September 07, 2023 09:23 AM
From: Jeff Bennett
Subject: Capturing request from API Connect 2018 deployed on OpenShift
I'd like to capture a request as it leaves API Connect in 2018 that's deployed in OpenShift. We have a request we're sending to a vendor. When we make the call direct to the vendor, it works. When we make the call to the vendor through API Connect, we're getting a 400 (Bad Request) error. We're using the same body for both requests. What we're trying to determine is when it leaves if it's being manipulated at all. I can login to DP within Openshift, but it seems it's not as straightforward as turning on probe etc (in this setup). Has anyone had experience with this?
------------------------------
Jeff Bennett
------------------------------