Handling GET /favicon.ico HTTP/1.1 Requests | Community
Skip to main content
Rohan_Garg
Community Advisor
Community Advisor
September 14, 2022
Solved

Handling GET /favicon.ico HTTP/1.1 Requests

  • September 14, 2022
  • 2 replies
  • 8813 views

Hi All,

 

The logs in AEM Dispatcher and HTTPD Access are flooded with GET /favicon.ico.

 

My favicon is present in clientlibs and rendering correctly as seen on the page's HTML -

<link rel="icon" type="image/png" href="/etc.clientlibs/brandA/clientlibs/clientlib-favicon/resources/favicon-brandA-180x180.png">
<link rel="icon" type="image/png" href="/etc.clientlibs/brandA/clientlibs/clientlib-favicon/resources/favicon-brandA-32x32.png" sizes="32x32">
<link rel="icon" type="image/png" href="/etc.clientlibs/brandA/clientlibs/clientlib-favicon/resources/favicon-brandA-192x192.png" sizes="192x192">

 

Query - How can I handle these requests which are currently going to 404 ?

 

Please find both the logs (Access and Request Logs) below -

1. AEM Dispatcher -

[14/Sep/2022:13:36:04 +0000] [I] [cm-pyyyyy-ezzzzzz-aem-publish-696c599768-kdcc7] "GET /favicon.ico" 40410ms [publishfarm/0] [actionnone] publish-pyyyyy-ezzzzzz.adobeaemcloud.com
[14/Sep/2022:13:36:30 +0000] [I] [cm-pyyyyy-ezzzzzz-aem-publish-696c599768-ndc9d] "GET /favicon.ico" 4047ms [publishfarm/0] [actionnone] publish-pyyyyy-ezzzzzz.adobeaemcloud.com
[14/Sep/2022:13:36:33 +0000] [I] [cm-pyyyyy-ezzzzzz-aem-publish-696c599768-ndc9d] "GET /favicon.ico" 4047ms [publishfarm/0] [actionnone] publish-pyyyyy-ezzzzzz.adobeaemcloud.com
[14/Sep/2022:13:36:47 +0000] [I] [cm-pyyyyy-ezzzzzz-aem-publish-696c599768-ndc9d] "GET /favicon.ico" 4047ms [publishfarm/0] [actionnone] publish-pyyyyy-ezzzzzz.adobeaemcloud.com
[14/Sep/2022:13:37:08 +0000] [I] [cm-pyyyyy-ezzzzzz-aem-publish-696c599768-kdcc7] "GET /favicon.ico" 40410ms [publishfarm/0] [actionnone] publish-pyyyyy-ezzzzzz.adobeaemcloud.com
[14/Sep/2022:13:37:09 +0000] [I] [cm-pyyyyy-ezzzzzz-aem-publish-696c599768-ndc9d] "GET /favicon.ico" 4047ms [publishfarm/0] [actionnone] publish-pyyyyy-ezzzzzz.adobeaemcloud.com
[14/Sep/2022:13:37:16 +0000] [I] [cm-pyyyyy-ezzzzzz-aem-publish-696c599768-ndc9d] "GET /favicon.ico" 4047ms [publishfarm/0] [actionnone] publish-pyyyyy-ezzzzzz.adobeaemcloud.com

 

2. HTTPD Access Logs -

cm-pyyyyy-ezzzzzz-aem-publish-696c599768-kdcc7 - - 14/Sep/2022:13:36:04 +0000 "GET /favicon.ico HTTP/1.1" 404 212 "https://publish-pyyyyy-ezzzzzz.adobeaemcloud.com/systemready" "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/72.0.3626.121 Safari/537.36"
cm-pyyyyy-ezzzzzz-aem-publish-696c599768-ndc9d - - 14/Sep/2022:13:36:30 +0000 "GET /favicon.ico HTTP/1.1" 404 212 "https://publish-pyyyyy-ezzzzzz.adobeaemcloud.com/systemready" "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/72.0.3626.121 Safari/537.36"
cm-pyyyyy-ezzzzzz-aem-publish-696c599768-ndc9d - - 14/Sep/2022:13:36:33 +0000 "GET /favicon.ico HTTP/1.1" 404 212 "https://publish-pyyyyy-ezzzzzz.adobeaemcloud.com/systemready" "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/72.0.3626.121 Safari/537.36"
cm-pyyyyy-ezzzzzz-aem-publish-696c599768-ndc9d - - 14/Sep/2022:13:36:47 +0000 "GET /favicon.ico HTTP/1.1" 404 212 "https://publish-pyyyyy-ezzzzzz.adobeaemcloud.com/systemready" "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/72.0.3626.121 Safari/537.36"
cm-pyyyyy-ezzzzzz-aem-publish-696c599768-kdcc7 - - 14/Sep/2022:13:37:08 +0000 "GET /favicon.ico HTTP/1.1" 404 212 "https://publish-pyyyyy-ezzzzzz.adobeaemcloud.com/systemready" "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/72.0.3626.121 Safari/537.36"
cm-pyyyyy-ezzzzzz-aem-publish-696c599768-ndc9d - - 14/Sep/2022:13:37:09 +0000 "GET /favicon.ico HTTP/1.1" 404 212 "https://publish-pyyyyy-ezzzzzz.adobeaemcloud.com/systemready" "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/72.0.3626.121 Safari/537.36"
cm-pyyyyy-ezzzzzz-aem-publish-696c599768-ndc9d - - 14/Sep/2022:13:37:16 +0000 "GET /favicon.ico HTTP/1.1" 404 212 "https://publish-pyyyyy-ezzzzzz.adobeaemcloud.com/systemready" "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/72.0.3626.121 Safari/537.36"

 

@arunpatidar@joerghoh, @kunal_gaba_, @b_sravan, @mohit_kbansal, @kautuk_sahni, @asutosh_jena_ 

 

Thanks,

Rohan Garg

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 Mohit_KBansal

@rohan_garg Usually browser/search engines make favicon request under root domain, ie. /favicon.ico

 

I suggest you add a redirect rule to handle this request

 

RewriteRule ^/favicon.ico$/etc.clientlibs/brandA/clientlibs/clientlib-favicon/resources/favicon-brandA-32x32.png [PT,NC,L]

 

* Just test if .ico will work with .png response.

 

2 replies

Mohit_KBansal
Adobe Employee
Mohit_KBansalAdobe EmployeeAccepted solution
Adobe Employee
September 14, 2022

@rohan_garg Usually browser/search engines make favicon request under root domain, ie. /favicon.ico

 

I suggest you add a redirect rule to handle this request

 

RewriteRule ^/favicon.ico$/etc.clientlibs/brandA/clientlibs/clientlib-favicon/resources/favicon-brandA-32x32.png [PT,NC,L]

 

* Just test if .ico will work with .png response.

 

Rohan_Garg
Community Advisor
Community Advisor
September 14, 2022

Hi Mohit, Thanks for the quick reply!

I had added the below rule which did not work -

 

#Rewrite Rule for Favicon
RewriteRule "^/favicon.ico" "/etc.clientlibs/brandA/clientlibs/clientlib-favicon/resources/favicon-brandA-180x180.png" [PT,L]

 

Any issue with the above redirect rule you think ?

Mohit_KBansal
Adobe Employee
Adobe Employee
September 15, 2022

Avoid quote " in your syntax

RewriteRule ^/favicon.ico$/etc.clientlibs/brandA/clientlibs/clientlib-favicon/resources/favicon-brandA-32x32.png [PT,NC,L]
B_Sravan
Community Advisor
Community Advisor
September 14, 2022

Hi @rohan_garg,

 

Firstly, I assume that you might have already considered writing a rewrite rule, if not – see if this example helps as reference.

RewriteCond %{REQUEST_URI} ^/favicon.ico$
RewriteRule ^/favicon.ico$ /content/dam/<folder-name>/favicon.ico [NC,PT]

Secondly, even though you have a correct rewrite rule, make sure your "/etc.clientlibs/brandA/clientlibs/clientlib-favicon/resources/favicon*" (your favicon path) is not blocked, as we usually block the etc/* paths.

Thirdly, I would suggest moving your client libs to apps and that is what even Adobe suggests and make use of allow proxy property to get access to your resources folder under client libs.

Rohan_Garg
Community Advisor
Community Advisor
September 15, 2022

Hi Sravan, Thank you for your response.

Our clientlibs are already present in /apps/projectFolder/clientlibs with allowProxy set to true.

 

The etc.clientlibs is not blocked but rather allowed in our filter rules.

I will give the rewrite rule to /content/dam/brandsA/favicon.ico and place a dummy asset in DAM.

Will let you know how it works out! Thanks!

Rohan_Garg
Community Advisor
Community Advisor
September 15, 2022

Update - The issue is still not resolved -

 

HTTPD Access Logs -

cm-pxyzxy-exyzxyz-aem-publish-859d67ddf9-fvjlv - - 15/Sep/2022:07:25:05 +0000 "GET /favicon.ico HTTP/1.1" 404 212 "https://publish-p57852-e459121.adobeaemcloud.com/systemready" "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/72.0.3626.121 Safari/537.36"

 

AEM Dispatcher Logs -

[15/Sep/2022:07:25:05 +0000] [I] [cm-pxyzxy-exyzxyz-aem-publish-859d67ddf9-fvjlv] "GET /favicon.ico" 40411ms [publishfarm/0] [actionnone] publish-pxyzxy-exyzxyz.adobeaemcloud.com