Check the gateway.log for more detailed error message - a 400 bad request typically has some additional error message as it represents a bad request. The only header that would trigger such a message from Knox itself when missing that I can recall is for when the WebAppSec provider is enabled for CSRF protection. The gateway-audit.log should show you whether the 400 is coming from the dispatch call to the backend service (so the service itself) or from Knox.
If you share those log entries - scrub hostnames and any sensitive info in there - we may be able to help. On Mon, Feb 7, 2022 at 3:39 AM Akshay Jain <[email protected]> wrote: > Hey Larry > Thanks for checking in. We have made some progress however > we're stuck with another conundrum. The way things work today in our > project is that the gateway endpoint undergoes three URL variations from > the source of the call. This includes having Nginx in between that does the > rewrite. For some reason, the Nginx URL changes the curl header and has > always been doing that. But for some reason, the new Knox update from 1.4.0 > to 1.6.0 is not taking that change positively and resulting in a 400 Error > back. We are working our way through the problem to find more details and I > will keep you posted if we find anything conclusive. Meanwhile, if > something just clicks on you and feels like there was a specific change in > regard to how CURL headers are addressed within Knox, please let me know. > Any help would be appreciated. And again thanks so much for checking back > with us, specially in this time and age where things are not, let's just > say, in the best of state :-) > > Regards. > Akshay Kotecha Jain (AK) > Phone: (+91) 7304653754 (India), (+1) 949.899.7556 (US) > Office: (+1)408.463.5850 > <https://www.linkedin.com/in/akshay-kotecha-jain-6a2574116> > > *> The hardest thing about the road not taken is that you never know where > it might have led.* > > > > On Tue, 25 Jan 2022 at 22:19, larry mccay <[email protected]> wrote: > >> All - >> >> I ended up finding the following in my spam folder requiring moderation >> to allow on to the dev@ list. It seems perhaps it was too old for the >> accept response to work, so I am just copying it here for Akshay. >> >> @Akshay Jain - please consider subscribing to the mailing list so that >> your interactions don't require moderation and you see all the responses >> properly. >> >> I think we will need more detail in order to help you here. >> While we don't generally do calls, we should be able to make some >> progress with more details of what is failing. >> >> thanks! >> >> --larry >> >> >> From: Akshay Jain <[email protected]> >> To: [email protected] >> Cc: >> Bcc: >> Date: Tue, 18 Jan 2022 21:43:45 +0530 >> Subject: Knox 1.4.0 to 1.6.1 upgrade support >> Hello >> I have been trying to upgrade a product gateway from Knox 1.4.0 to Knox >> 1.6.1 and have been having trouble while trying to start the gateway. All I >> see in the gateway.err log file is "No Console". I am not sure how to >> proceed from this point and could really use some help. If someone in the >> community is willing to help please let me know and I will set up a call at >> your convenience. >> >> Regards. >> Akshay Kotecha Jain (AK) >> Phone: (+91) 7304653754 (India), (+1) 949.899.7556 (US) >> Office: (+1)408.463.5850 >> >
