Issue with HTTP Status 400 - Bad Request when sending email campaigns

[MarilagM3]

I am writing to bring to your attention an issue I have been experiencing today. I have been unable to send the Zoom link to the participants as I keep receiving an HTTP Status 400 – Bad Request error.

This is a time-sensitive matter, as I need to provide the Zoom link to all the attendees in a timely manner. I would greatly appreciate if you could please look into this problem and provide a resolution as soon as possible.

Thank you in advance for your assistance. I am available should you require any additional information from me.

[Courtney_E]

Hello MarilagM3,

Thank you for reaching out to Constant Contact API Developer Support. My team is here to assist outside software developers with questions about building into Constant Contact's API.

If you are still experiencing issues with this, please reach out to our team directly/securely via email at webservices@constantcontact.com referencing case 32520101 with: The API key (or name of the integration) that you are using, and the username of the account that you are trying to publish the emails to so that we can take a look at our logs and assist further.

Please have a look and let us know if you have any other questions!

[ColinHuronCoC]

I have gotten this 400 HTTP error on every email send for the last few weeks... the emails seem to be going out regardless, so I haven't been too worried about it.  I'm not using any APIs, this is directly on the CC website.

[Courtney_E]

Hello ColinHuronCoC,

Thank you for reaching out to Constant Contact API Developer Support. My team is here to assist outside software developers with questions about building into Constant Contact's API.

I was able to find an open ticket for this issue, and it looks like a fix was pushed out on 7/14/24. 

The ticket also notes that if you are still experiencing the issue, that it is likely due to stored cache/cookies from prior to the fix, and that clearing the cache/cookies for the time range of "all time" should fix the issue.

If you have further questions regarding this issue, please reach out to Constant Contact's Support Team at 866-289-2101 and reference case #32626962.

Please have a look and let us know if you have any other questions!

[ColinHuronCoC]

This issue went away for a time, but is back now, occurring on every email campaign send.

[user99160]

I am also have this exact issue - the emails appear to be going out but every email I send defaults to this page

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:770)
	org.apache.coyote.http11.Http11InputBuffer.parseHeader(Http11InputBuffer.java:964)
	org.apache.coyote.http11.Http11InputBuffer.parseHeaders(Http11InputBuffer.java:591)
	org.apache.coyote.http11.Http11Processor.service(Http11Processor.java:286)
	org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:63)
	org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:928)
	org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1794)
	org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:52)
	org.apache.tomcat.util.threads.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1191)
	org.apache.tomcat.util.threads.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:659)
	org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
	java.lang.Thread.run(Thread.java:750)

Note The full stack trace of the root cause is available in the server logs.

---

Apache Tomcat (TomEE)/9.0.82 (8.0.16)