Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
BedrockMission!

Learn More

View all

Sign in to view all badges

AEM 6.5 HEAD Requests

Avatar

Avatar
Validate 10
Level 3
crisr1
Level 3

Likes

16 likes

Total Posts

75 posts

Correct Reply

5 solutions
Top badges earned
Validate 10
Validate 1
Ignite 5
Ignite 3
Ignite 1
View profile

Avatar
Validate 10
Level 3
crisr1
Level 3

Likes

16 likes

Total Posts

75 posts

Correct Reply

5 solutions
Top badges earned
Validate 10
Validate 1
Ignite 5
Ignite 3
Ignite 1
View profile
crisr1
Level 3

12-03-2021

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.

AEM 6.5 author Error

Accepted Solutions (0)

Answers (2)

Answers (2)

Avatar

Avatar
Give Back 100
Level 10
asutosh_jena
Level 10

Likes

544 likes

Total Posts

663 posts

Correct Reply

190 solutions
Top badges earned
Give Back 100
Boost 500
Affirm 100
Ignite 1
Establish
View profile

Avatar
Give Back 100
Level 10
asutosh_jena
Level 10

Likes

544 likes

Total Posts

663 posts

Correct Reply

190 solutions
Top badges earned
Give Back 100
Boost 500
Affirm 100
Ignite 1
Establish
View profile
asutosh_jena
Level 10

15-03-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!

Avatar

Avatar
Coach
Employee
Jörg_Hoh
Employee

Likes

1,111 likes

Total Posts

3,145 posts

Correct Reply

1,072 solutions
Top badges earned
Coach
Give back 600
Ignite 5
Ignite 3
Ignite 1
View profile

Avatar
Coach
Employee
Jörg_Hoh
Employee

Likes

1,111 likes

Total Posts

3,145 posts

Correct Reply

1,072 solutions
Top badges earned
Coach
Give back 600
Ignite 5
Ignite 3
Ignite 1
View profile
Jörg_Hoh
Employee

13-03-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

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.