Hi,
We recently started running into an issue where everyday the dispatcher would cache some file with -wrong appended it it, ex. home-wrong.html and home-wrong2.html. This ends up being served on the site.
Has anyone run into such issues. We have not had any code or dispatcher changes deployed and suddenly started running into this issue.
Thanks,
Har**bleep**
Solved! Go to Solution.
Views
Replies
Total Likes
Enable Debug logs in Dispatcher to get more information on caching of wrong files, that might provide some information.
https://blogs.perficient.com/2017/10/12/mastering-aem-dispatcher-part-1-debugging-the-dispatcher/
@hhk_hsb seems like some issue with publisher maybe as you are confirming no code deployed to dispatchers.
Have you touched any of your link rewriters, sling:alias, sling:redirects etc..?
Hi Shashi,
So we have code deployed, but we did not deploy any new changes. I tried looking at publisher logs but do not see any issue there as well.
Enable Debug logs in Dispatcher to get more information on caching of wrong files, that might provide some information.
https://blogs.perficient.com/2017/10/12/mastering-aem-dispatcher-part-1-debugging-the-dispatcher/
Hi,
Please check the request logs?
It seems there are sling mapping which are resolving the actual resource even with -wrong2 postfix.
can you verify any changes might have done at the Resource Resolver Factory in configMgr or mapping level or for vanity URL of your publishers?
if more than one publisher, then verify whether it is happening for all the publisher or not?
Hope this helps..!
Umesh Thakur
Turns out there was http hijacking attack on our server and the support engineer had renamed the corrupted files for investigation.