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
  • 13205 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.

       

        bmccurdy1
        bmccurdy1
        Level 2
        February 22, 2021
        I think someone else may have already mentioned it, but on your publisher(s) double-check the OSGi config for Apache Sling Referrer Filter and ensure you are allowing the methods you are trying to support.
          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...