400 bad request error possibly with Zendesk proxy server



2024년 1월 30일에 게시됨

Hey, so I'm running into a unique issue with a 400 bad request error and it's coming down to using the Zendesk Proxy Server in the app I'm building.

So I have the proxy server hitting a post api request in prod and staging. I'm passing in strings to the api calls to get a json object response back. This seems to work fine when I pass in strings that are around 1500 characters or less, but when I pass something longer than that, the proxy server doesn't seem to hit the api at all. I've added console logs to the api it is trying to reach and I haven't seen those logs being called when sending the request via the proxy server. So I know for sure its not being reached.

Even stranger, when I test this in a local environment, the proxy server doesn't run into this issue at all and returns a 200 response as expected.

It doesn't seem to be an issue with a character not being parsed or encoded before the call is made. So I've ruled that out. I've attempted to simplify the request by passing in "Lorem Ipsum" strings of different lengths and it feels like passing in a long path to the proxy server is the only explanation for the 400 error. However, because it's succeeding locally, it has mean very confused what the cause could be.

Been trying everything to troubleshoot this to see if it's anything on my end that could be causing the issue, but the code is all the same across local, staging, and production.

Any help would be greatly appreciated.


0

0

댓글 0개

로그인하세요.

원하는 정보를 못 찾으셨나요?

새 게시물