csrf token are successfully generated at AEM stage environment both author and publishers.
The problem is coming probably at dispatcher or CDN level. I am not sure where to look further to resolve this issue.
At dispatcher level , I can see following logs:
[Wed May 08 02:32:00 2024] [D] [pid 11304 (tid 11668)] checking [/libs/granite/csrf/token.json]
[Wed May 08 02:32:00 2024] [D] [pid 11304 (tid 11668)] request URL not in cache rules: /libs/granite/csrf/token.json
[Wed May 08 02:32:00 2024] [D] [pid 11304 (tid 11668)] cache-action for [/libs/granite/csrf/token.json]: NONE
Above logs conclude that the token is not cached at dispatcher<OK>
And also in logs I can see following which is where I am looking for help :
[Wed May 08 02:32:00 2024] [D] [pid 11304 (tid 11668)] Name not in ignored URL parameters ACL: 404;http://secure-stage.abc.info:80/libs/granite/csrf/token.json
[Wed May 08 02:32:00 2024] [D] [pid 11304 (tid 11668)] request contains a query string: 404;http://secure-stage.abc.info:80/libs/granite/csrf/token.json
Strangely I have checked at PROD environment, with similar configuration at CDN and dispatcher level, the csrf token is generated properly.
I am suspecting the issue might be there at IIS server (used for hosting application), dispatcher or CDN.
Can anyone help here?
Solved! Go to Solution.
Topics help categorize Community content and increase your ability to discover relevant content.
Views
Replies
Total Likes
Hi @MaheshKPati
404 errors are usually returned from dispatcher when the specific URL is blocked or not allowed to pass to publishers.
Can you please take a look at you dispatcher filter configuration to see if the below is there . Under dispatcher.d filter file you can check .
/00xx { /type "allow" /method "GET" /url '/libs/granite/csrf/token.json' /extension 'json' }
Hi @MaheshKPati
404 errors are usually returned from dispatcher when the specific URL is blocked or not allowed to pass to publishers.
Can you please take a look at you dispatcher filter configuration to see if the below is there . Under dispatcher.d filter file you can check .
/00xx { /type "allow" /method "GET" /url '/libs/granite/csrf/token.json' /extension 'json' }
Hi @sherinregi ,
This line is already present. Even if i bypass dispatcher, this issue exists.
Let me look into the CDN or IIS rules.
Views
Replies
Total Likes
Hi @MaheshKPati ,
The issue you're encountering, where access to the CSRF token path /libs/granite/csrf/token.json returns a 404 error, seems to be related to the configuration or behavior of your dispatcher or CDN setup. Here are some steps you can take to diagnose and resolve the issue:
Verify Dispatcher Configuration:
Check Dispatcher Rules:
Examine CDN Configuration:
Inspect IIS Server Configuration:
Compare Environments:
Test Direct Access:
Logging and Monitoring:
By systematically reviewing and troubleshooting each component of your setup, you should be able to identify and resolve the issue with accessing the CSRF token path. If you're still unable to resolve the issue, consider reaching out to your CDN or Dispatcher provider for further assistance.
Views
Likes
Replies
Views
Likes
Replies