Request Payload getting empty while executing POST servlet on AEM Cloud Service Publish Instance | Community
Skip to main content
N
NehaMa
Level 4
July 24, 2026
Question

Request Payload getting empty while executing POST servlet on AEM Cloud Service Publish Instance

  • July 24, 2026
  • 3 replies
  • 120 views

We are facing issue on AEM as Cloud Service Publish instance where request payload is empty when triggered path based POST servlet. Request is reaching servlet as enabled in dispatcher but in servlet logs we are seeing headers as 

Content-Type as null, Content-Length as 0 and No request payload found which is causing servlet to fail.

On Author the servlet is working fine.

Any suggestions in this regard will be helpful

3 replies

N
NehaMaAuthor
Level 4
July 25, 2026

hi ​@arunpatidar - Kindly suggest

arunpatidar
Community Advisor
arunpatidarCommunity Advisor
Community Advisor
July 28, 2026

Hi Neha,
Can you please check if the issue is due to CDN or WAF? Are you calling servlet using custom domain or publish domain? How does the servlet path looks like?

Maybe try below

Send the identical POST request to both endpoints:

 
curl -v \
  -X POST \
  "https://publish-p<program-id>-e<environment-id>.adobeaemcloud.com/bin/my-servlet" \
  -H "Content-Type: application/json" \
  --data-raw '{"test":"value"}'

Then test the custom domain:

curl -v \
  -X POST \
  "https://www.example.com/bin/my-servlet" \
  -H "Content-Type: application/json" \
  --data-raw '{"test":"value"}'


Can you also check if there is any redirect rule, which might causing the issue?
 

Arun Patidar
chaudharynick
chaudharynick
Level 4
July 27, 2026

Since the servlet works on Author but receives Content-Type = null, Content-Length = 0, and an empty request body only on Publish, it appears the request entity isn’t reaching AEM.

I’d investigate the request path (CDN → Dispatcher → Publish) to see if the request body or related headers are being stripped or not forwarded. In particular, check:

  • Whether there’s an HTTP → HTTPS redirect (or any other redirect) before the request reaches AEM, as redirects can result in the body being lost.
  • Any custom Dispatcher, CDN, load balancer, or WAF configuration that could be affecting POST requests.

Could you also check:

  • If there is any redirect that is changing the request from POST to GET
  • Any other POST servlet working
  • The Dispatcher filter/virtual host configuration for this endpoint 
  • Whether there’s any custom CDN, reverse proxy, or WAF in front of AEM Publish.
Terms & ConditionsAccessibility statement

Loading footer...