AEM 6.5 HEAD Requests | Community
Skip to main content
crisr1
crisr1
Level 4
March 12, 2021
Solved

AEM 6.5 HEAD Requests

  • March 12, 2021
  • 2 replies
  • 2468 views

AEM 6.5 seems to be making regular requests such as the one below; as found in access.log from a publish instance

 

"HEAD / HTTP/1.1" 200 - "-" "Apache-HttpClient/4.5.4 (Java/1.8.0_251)"

 

The polling fails constantly on author instances, and the error rate shows up in Java reporting such as New Relic. According to NR, the error is 401 on author instances. The errors reported in New Relic have identifiers (qtp631235405-15166) that match the log below.

 

*INFO* [qtp631235405-15166] org.apache.sling.auth.core.impl.SlingAuthenticator getAnonymousResolver: Anonymous access not allowed by configuration - requesting credentials

 

What is generating these HTTP HEAD requests, and is there a way to turn off whatever is making these requests?

 

Thanks for your comments and question.

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 Asutosh_Jena_

Hi @crisr1 

Could you please provide some more information here. I personally have never seen this type of request on AEM publish instances.
Suspect it might be something that will be coming from dispatcher but will be able to look further more once you provide some more information.

Thanks!

2 replies

joerghoh
Adobe Employee
joerghohAdobe Employee
Adobe Employee
March 13, 2021

Are you really sure that these requests come from AEM itself? Have you ruled out all possibilities that it can come in via dispatcher? What's the interval in which these queries show up?

 

It doesn't make sense for AEM to send such a request to itself, and I haven't seen something like this yet. At least there's nothing ootb which does that.

    crisr1
    crisr1Author
    Level 4
    March 19, 2021

    I don't think it's coming through the dispatcher. There are some head requests in the disp, but at a much lower interval and with a different user agent signature

     

    Monitoring the publisher, a few requests comes every 30s

    tail -f /mnt/crx/publish/crx-quickstart/logs/access.log | grep --line-buffered HEAD

    "HEAD / HTTP/1.1" 200 - "-" "Apache-HttpClient/4.5.4 (Java/1.8.0_251)"

     

    Monitor the dispatcher logs shows a different HEAD request; interval about ~130s

    tail -f /mnt/var/log/httpd/access_log | grep --line-buffered HEAD

    "HEAD / HTTP/1.1" 200 - "-" "Mozilla/5.0 (X11; Linux x86_64)...

     

    I think there's a health check executed regularly with a signature like org.apache.sling.commons.scheduler.impl.NonParallelQuartzJobExecutor.execute() that's causing it, but probably I'll never know for sure.

     

    The dispatcher does get some HEAD requests, but the browser agent is different Mozilla/5.0 (X11; Linux x86_64), not Apache-HttpClient/4.5.4. The dispatcher does shows some other "health check" requests that come at a regular interval from the same client, but these route externally, I know how to configure those and disable them.

     

     

    Asutosh_Jena_
    Community Advisor
    Asutosh_Jena_Community AdvisorAccepted solution
    Community Advisor
    March 15, 2021

    Hi @crisr1 

    Could you please provide some more information here. I personally have never seen this type of request on AEM publish instances.
    Suspect it might be something that will be coming from dispatcher but will be able to look further more once you provide some more information.

    Thanks!

      crisr1
      crisr1Author
      Level 4
      March 15, 2021

      It is something new I found in AEM 6.5.7 author and publisher instances. It's not present in our previous AEM 6.4.8.3 environments. The user agent mentioned in the HEAD request mentioned Apache-HttpClient/4.5.4 (Java/1.8.0_251), so I doubt that it is originating from the dispatcher. But at the same time, I do not see the same activity in localhost 6.5 instances.

      Terms & ConditionsAccessibility statement

      Loading footer...