Servlet Calls 204 error in AEM 6.5

Avatar

Avatar

santhoshm687661

Avatar

santhoshm687661

santhoshm687661

19-02-2021

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

Replies

Avatar

Avatar

davidjgonzalezzzz

Avatar

davidjgonzalezzzz

davidjgonzalezzzz

26-02-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?

Avatar

Avatar

santhoshm687661

Avatar

santhoshm687661

santhoshm687661

27-02-2021

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.

Avatar

Avatar

santhoshm687661

Avatar

santhoshm687661

santhoshm687661

01-03-2021

I am not seeing any errors related to the CORS in console.

I have logged the response headers from app but am not seeing any errors in the logs.

 

@davidjgonzalezzzz Please suggest.

 

 

Avatar

Avatar

santhoshm687661

Avatar

santhoshm687661

santhoshm687661

01-03-2021

@davidjgonzalezzzz I have did some changes and tested the servlets with POST calls with 200 in publisher but 204 in dispatcher and akamai.

 

I am expecting there is an issue with dispatcher.

 

But the same configuration has been worked for vanila upgrade.Can you suggest is there any specific that i need to check.

 

/0111 { /type "allow" /url "/bin/test/test/*" }
/0113 { /type "allow" /url "/bin/test/test/*" }

 

The above parameters have been allowed in the dispatcher.any.Please let me know if i miss anything in the dispatcher.

 

Thanks,

Santhosh

Avatar

Avatar

santhoshm687661

Avatar

santhoshm687661

santhoshm687661

01-03-2021

Please find the attached logs from dispatcher.

@davidjgonzalezzzz 

Avatar

Avatar

santhoshm687661

Avatar

santhoshm687661

santhoshm687661

02-03-2021

In edge version 44 and below i am not seeing any issue with POST calls i.e. 204 error code.

 

In chrome am seeing the issue 204 error code and with all the updated versions of the browsers.

 

@davidjgonzalezzzz @bmccurdy1 Please suggest204edge.PNG