apple-touch-icon 404 | Community
Skip to main content
S
SanthoshAs1
Level 2
September 1, 2023
Solved

apple-touch-icon 404

  • September 1, 2023
  • 3 replies
  • 3136 views

Hi, 

I have been recently looking into our publisher logs and found that our logs are loaded with 404 from app-touch-icon not being found. Searched online and found that its being automatically requested from apple mobile devices. Is it to filter these kind of request in dispatcher. Could someone guide/help me with this ?

Logs:
31.08.2023 00:06:21.428 *INFO* [91.66.109.77 [1693440381423] GET /content/lass/published-sites/de/de/apple-touch-icon-120x120.png HTTP/1.1] org.apache.sling.engine.impl.SlingRequestProcessorImpl service: Resource /content/lass/published-sites/de/de/apple-touch-icon-120x120.png not found

 

Thanks

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 Rohit_Utreja

@santhoshas1 

Yes, it has been requested by the device.

You can refer /libs/core/wcm/components/page/v3/page/head.resources.html.

If you are inheriting this component in your page level components, than you can overwrite this too.

3 replies

Preetpal_Bindra
Community Advisor
Preetpal_BindraCommunity Advisor
Community Advisor
September 1, 2023

Hello @santhoshas1 ,

You are correct. These images are requested by the devices.

We had a similar situation.

These could either be,

1. excluded from Dispatcher by adding rules to prevent forwarding the request to AEM publish servers, or,

2. upload an apple touch icon at the location seen in the logs into AEM dam and simply publish it making it a HTTP 200 response.

 

There is one other way I can think of, but will not recommend it. That is redirecting the touch icon request to a cached 404 page in dispatcher.

 

Hope that helps!

 

Regards,

Preetpal

    S
    SanthoshAs1Author
    Level 2
    September 1, 2023

    Thanks Preetpal, I will use dispatcher filters to filter out these

      EstebanBustamante
      Community Advisor and Adobe Champion
      EstebanBustamanteCommunity Advisor and Adobe Champion
      Community Advisor and Adobe Champion
      September 1, 2023

      It seems that there might be an issue related to the favicons on your website, which appears to be improperly managed. By default, certain devices and browsers request specific types, formats, and sizes of favicons for their applications. For instance, some iPhones and iPads require a high-resolution favicon to accommodate their retina screens. Due to these factors, it's advisable to have various versions of your favicon readily available.

       

      I recommend reading this article: https://sympli.io/blog/heres-everything-you-need-to-know-about-favicons-in-2020. Afterward, you can automatically generate your favicons using a free web tool, such as https://realfavicongenerator.net/.

       

      Hope this helps.

      Esteban Bustamante
        Rohit_Utreja
        Community Advisor
        Rohit_UtrejaCommunity AdvisorAccepted solution
        Community Advisor
        September 1, 2023

        @santhoshas1 

        Yes, it has been requested by the device.

        You can refer /libs/core/wcm/components/page/v3/page/head.resources.html.

        If you are inheriting this component in your page level components, than you can overwrite this too.

          S
          SanthoshAs1Author
          Level 2
          September 1, 2023

          We have overwritten it to this 

          <template data-sly-template.favicons="${ @ path ='/etc.clientlibs/lass/clientlibs/clientlib-libs/resources/icons', additionalPage }">
            <meta content="${path}/favicon-${additionalPage.brand}.ico" name="msapplication-TileImage" />
            <link href="${path}/favicon-${additionalPage.brand}.ico" rel="shortcut icon" type="image/x-icon" />
            <link href="${path}/favicon-${additionalPage.brand}.ico" rel="apple-touch-icon" sizes="152x152" />
          </template>
            Terms & ConditionsAccessibility statement

            Loading footer...