Dispatcher is caching incorrect files with -wrong appended to it | Community
Skip to main content
H
hhk_hsb
February 7, 2023
Solved

Dispatcher is caching incorrect files with -wrong appended to it

  • February 7, 2023
  • 6 replies
  • 1419 views

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**

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by indranilm

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/ 

6 replies

Shashi_Mulugu
Community Advisor
Shashi_MuluguCommunity Advisor
Community Advisor
February 7, 2023

@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..?

    H
    hhk_hsbAuthor
    February 7, 2023

    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.

      I
      indranilmAccepted solution
      Level 2
      February 8, 2023

      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/ 

        arunpatidar
        Community Advisor
        arunpatidarCommunity Advisor
        Community Advisor
        February 8, 2023

        Hi,

        Please check the request logs?

        It seems there are sling mapping which are resolving the actual resource even with -wrong2 postfix.

        Arun Patidar
          Umesh_Thakur
          Community Advisor
          Umesh_ThakurCommunity Advisor
          Community Advisor
          February 8, 2023

          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

            H
            hhk_hsbAuthor
            February 10, 2023

            Turns out there was http hijacking attack on our server and the support engineer had renamed the corrupted files for investigation.

              Terms & ConditionsAccessibility statement

              Loading footer...