Getting 204-No Content from response of any POST Servlet call | Community
Skip to main content
D
dbiswas-inT
December 27, 2023
Solved

Getting 204-No Content from response of any POST Servlet call

  • December 27, 2023
  • 2 replies
  • 3057 views

Hi,

 

We have created first POST type Servlet call in my current project, and getting 204-No content in response. In Publisher environment, it is throwing 200 as expected. But, as we used Akamai for cache management, in Akamai URL, it is throwing this error.

 

We investigated further and found in Akamai URL, for all POST servlet calls, a Header Parameter named "Origin" got added with the value, domain name of the Akamai URL. Same issue we can replicate in POSTMAN also, when we are adding "Origin" with value - domain name of the Akamai URL in Header, it is throwing 204-No content. But if we remove that from Header in POSTMAN call, then only we are getting proper response.

 

We tried but unable to discard that header parameter "Origin" at the time of POST servlet call. From publisher environment, this header parameter is not getting added.

 

Is there any way to discard that parameter in POST Servlet call from Akamai URL ?

I have added Akamai URL' domain in the value of "alloworigin" parameter of CORS Policy config and also added the path in the value of "allowedpaths" parameter in same config.

 

Please let me know if anyone have any solution of this issue..

 

Thanks.

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by joerghoh

Thanks! But that does not look somehow problematic, can you exclude the chance that it has something to do with the custom code?

And just to confirm:

  • When you do that post (without the Origin header) to the AEM publish domain directly (bypassing Akamai), you get the expected result.
  • And when you do the very same post (without the Origin header) to the Akamai domain, you get the statuscode 204.

 

Some more checks I would recommend:

  • Have you checked the logs of the AEM instances/dispatchers to see if that request actually reached AEM?
  • Can you replicate this behavior in a different AEM environment as well?
  • How does it behave on your local development environment (or on a RDE) when you the request with the Origin header. Do you get a 204 as well?
  • Do you see this origin header also for other requests hitting AEM?

 

 

 

2 replies

Preetpal_Bindra
Community Advisor
Preetpal_BindraCommunity Advisor
Community Advisor
December 27, 2023

Hello @dbiswas-int ,

 

Does the servlet does its work it is intended to, regardless of its HTTP response? Meaning, does it execute without any error?

or

Is it just a concern about why the response codes are different with AEM Publisher v/s Akamai?

 

thanks,

Preetpal

    D
    dbiswas-inTAuthor
    December 28, 2023

    Hi @preetpal_bindra ,

    The servlet does work in Publisher Environment with proper response, but in Akamai URL it is giving blank response, with status code 204-No content.

     

    As I looked further and found that from Akamai URL, when we are calling that servlet, the origin parameter is added(not sure where is the source of this add). In Publisher environment, it is not added.

    I also checked from POSTMAN. When I am manually adding this origin parameter, same 204 response code is showing with blank response. But, when I am manually discarding that from the call, then only the response is coming correctly.

    The issue is basically this blank response. 

      joerghoh
      Adobe Employee
      joerghohAdobe Employee
      Adobe Employee
      December 29, 2023

      can you please paste the curl command, which can show this situation? What AEM version are you using?

        D
        dbiswas-inTAuthor
        January 1, 2024

        AEM Version : 6.5

        cURL : This is the format below. Some data is changed due to client's non-discloser agreement.

        curl --location 'https://abc.com/services/category-menu/post-servlet' \ --header 'Origin: https://abc.com' \ --header 'Content-Type: application/json' \ --header 'Authorization: Bearer XXX' \ --header 'Cookie: _abck=23B8B8DF83CB9285F6AA9587FB4AC7F2~-1~YAAQE0w5F3TDK5+FAQAAr0FS95YqWh+lBHadGGXSqCDe83QXzuuRH6qYM18P5q2n8XypIxM/IQBIGHCYwPEywCR/PkYYmojLHQODC365L8pZYPETWElL/W729Y+dG2uPc/ms3ko4fUVMlWeH+Mq7pS3AkXuJIN3qUwcsK6XBhu4Yw8jpEiM+RcmzeW4xvRpMkLOswy8WSSXFidKpccvGrCsknG6Y4L5xSFm7YGC/rHyf7zsNMJZa4AfXT2GwO07wNZw4fbLC1X3g6Suod1H9W34A87S1dDMM7HR5JMMCx7O+WAvJRmITzqOf9E5+8EpA+lYDMtRrA5ImTaIjeK8qpMLhy1Iid0aXzjz8xP/l6oEw1WeDREm~-1~-1~-1; QA_ORIGIN=OLD; abE1=Y100; affinity="b9fb81e00119addc"' \ --data '{ "sku":"11171", "quantity":"2.0", "zipcode":"03833", "currentProductId":"11930", "existingProductIDs":"11930:2015", "field": "L2NvbnRlbnQvZGFtL3RzYy1hZW0tcGRwL2NvbnRlbnQtZnJhZ21lbnRzL2VuL2VzcG90cpb24tY2Y=", "stlocId":"161" }'

         

        Response : Blank

         

          joerghoh
          Adobe Employee
          joerghohAdobe EmployeeAccepted solution
          Adobe Employee
          January 1, 2024

          Thanks! But that does not look somehow problematic, can you exclude the chance that it has something to do with the custom code?

          And just to confirm:

          • When you do that post (without the Origin header) to the AEM publish domain directly (bypassing Akamai), you get the expected result.
          • And when you do the very same post (without the Origin header) to the Akamai domain, you get the statuscode 204.

           

          Some more checks I would recommend:

          • Have you checked the logs of the AEM instances/dispatchers to see if that request actually reached AEM?
          • Can you replicate this behavior in a different AEM environment as well?
          • How does it behave on your local development environment (or on a RDE) when you the request with the Origin header. Do you get a 204 as well?
          • Do you see this origin header also for other requests hitting AEM?

           

           

           

            Terms & ConditionsAccessibility statement

            Loading footer...