Servlet Calls 204 error in AEM 6.5 | Community
Skip to main content
S
santhoshm687661
Level 3
February 19, 2021

Servlet Calls 204 error in AEM 6.5

  • February 19, 2021
  • 5 replies
  • 13234 views

Hi All,

After upgrading to aem 6.5.6(inplace from 6.4.8.1.to 6.5.6) i am facing with POST and DELETE calls are going to 204 instead of 302 or 200.

 

Please let me know if any came across 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.

    5 replies

    D
    Adobe Employee
    davidjgonzalezzzzAdobe Employee
    Adobe Employee
    February 19, 2021
    Can you please add more details to this? Which POST requests exactly? What servlets are you hitting? What's going in the error.log?
      S
      santhoshm687661Author
      Level 3
      February 19, 2021

      https://castrolfastlane-supporttest-www.castrol.com/bin/downstream/fastlane/cart?productCode=3374721&quantity=5

       

      When am trying to hit with the above url am able to see the data.

       

      Whem am accessing through application after upgrade am facing this 204 issues am not able see any errors related to this servlet.

       

        D
        Adobe Employee
        davidjgonzalezzzzAdobe Employee
        Adobe Employee
        February 22, 2021

        @santhoshm687661can you please provide the Request Progress Log for this request? This should help shed quite a bit of light of what's going on - ex. does it stop processing at the CORS filter, or some other Filter, or is it resolving to the incorrect servlet, etc.


        There is no known issue with any version of AEM that turns non-204 responses to 204 responses. I understand that this used to work pre-upgrade and doesn't now - but you'll have to help w/ the investigation if you want to pinpoint and resolve the problem - else we're all just taking guesses 🙂

          S
          santhoshm687661Author
          Level 3
          February 27, 2021

          What sort of Application is this exactly? (SPA, Desktop app, mobile app?)

           

          Either way, this certainly sounds like what other mentioned, likely at an issue with:


          * CORS

          * Referrer Filter

          * CSRF Token 

           

          CORS seems like the most likely suspect. Can you log the response headers from your app?


          What sort of Application is this exactly? (SPA, Desktop app, mobile app?) -----Its a Desktop application

           

          Either way, this certainly sounds like what other mentioned, likely at an issue with:


          * CORS -- Have verified with 6.4 configuration's it looks same and in the vanila instance of 6.5 looks same there it works out.

          * Referrer Filter - Allowed Hosts has been checked and added the domains which were required for the applications.

          * CSRF Token - Have allowed POST and verified, but still i see the same issue and i have allowed the servlet in the excluded paths but it doesn't worked out.

           

          CORS seems like the most likely suspect. Can you log the response headers from your app?----This i haven't tried but we will check this.

           

          Thank you @davidjgonzalezzzz still if i miss any please let me know.

            D
            Adobe Employee
            davidjgonzalezzzzAdobe Employee
            Adobe Employee
            February 19, 2021

            Deleted response. See response in comment below.

              Uppari_Ramesh
              Uppari_Ramesh
              Level 5
              December 4, 2023

              Hi @santhoshm687661 ,

               

              Basically 204 response from your servlet indicates that you are missing your api endpoint in CORS policy Allowed paths section. Just add your servlet endpoint in Allowed paths section.

               

              Thanks,

              Ramesh

              Terms & ConditionsAccessibility statement

              Loading footer...