HTTP 400 error gathering stats based on JWT

Description
I am trying to gather stats for all the users in our account. For the purpose I need to make multiple calls as part of the same. The calls are working fine until few hundred users but starts failing after that.

Error
Receiving “400 Request Header Or Cookie Too Large” after few hundred successful calls.

Operation failed. Label: Fetch JsonRoot, Name: JsonRootFetch, Message: HttpResponse StatusCode was 400 .<!doctype html>HTTP Status 400 – Bad Requesth1 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:22px;} h2 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:16px;} h3 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:14px;} body {font-family:Tahoma,Arial,sans-serif;color:black;background-color:white;} b {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;} p {font-family:Tahoma,Arial,sans-serif;background:white;color:black;font-size:12px;} a {color:black;} a.name {color:black;} .line {height:1px;background-color:#525D76;border:none;}

HTTP Status 400 – Bad Request


Type Exception Report

Message Request header is too large

Description The server cannot or will not process the request due to something that is perceived to be a client error (e.g., malformed request syntax, invalid request message framing, or deceptive request routing).

Exception

java.lang.IllegalArgumentException: Request header is too large
org.apache.coyote.http11.Http11InputBuffer.fill(Http11InputBuffer.java:720)
org.apache.coyote.http11.Http11InputBuffer.parseHeader(Http11InputBuffer.java:867)
org.apache.coyote.http11.Http11InputBuffer.parseHeaders(Http11InputBuffer.java:573)
org.apache.coyote.http11.Http11Processor.service(Http11Processor.java:700)
org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:66)
org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:806)
org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1498)
org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:49)
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
java.lang.Thread.run(Thread.java:748)

API used “Get Meeting Reports”

There is no change the way headers and request are passed for successful and failed calls. Can there be that the zoom API is considering this as a spamming and as a security behaving like this or you believe this could be something at my end.

Hey @aaggarwa,

Please double check you are not exceeding our rate limits.

Thanks,
Tommy

Hi Tommy,

I checked that somehow my process was appending content type from previous call as part of every new request. Hence, after a certain limit it was getting too long for zoom API to process.

I have made changes at my end to reset the same as part of every call and it’s working fine now.

Thanks,
Abhishek Aggarwal

1 Like

Thanks for the follow up!

Happy to hear it is working! :slight_smile:

-Tommy