Bug 820941 - (rhq.plugins.www.util.WWWUtils)- Ping request returned a response with client error 403, but server returns 200
(rhq.plugins.www.util.WWWUtils)- Ping request returned a response with client...
Product: RHQ Project
Classification: Other
Component: Agent (Show other bugs)
Unspecified Unspecified
unspecified Severity low (vote)
: ---
: ---
Assigned To: RHQ Project Maintainer
Mike Foley
Depends On:
  Show dependency treegraph
Reported: 2012-05-11 07:46 EDT by Libor Zoubek
Modified: 2015-11-01 19:42 EST (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2012-05-14 18:00:58 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Libor Zoubek 2012-05-11 07:46:36 EDT
Description of problem: I am getting warnings from apache plugin in agent.log 

[ResourceContainer.invoker.daemon-58] (rhq.plugins.www.util.WWWUtils)- Ping request to [] returned a response with client error 403 (Forbidden)

When I try GET on I get 200-OK.

Version-Release number of selected component (if applicable):
RHQ 4.5-master

How reproducible:always

Steps to Reproduce:
1.import apache on linux
2.check agent.log

Expected results: warnings should disappear, since does not return 403
Comment 1 Larry O'Leary 2012-05-14 10:53:41 EDT
Is a redirect being used? What does the following produce:

wget --max-redirect=0

I am not sure if we would handle redirects. Additionally, if a proxy configuration is used, it could react differently to each client. How are you testing the URL when receiving the 200 OK? Also, what does the access.log and error.log reveal for the ping?
Comment 2 Libor Zoubek 2012-05-14 18:00:58 EDT
Not a bug. My mistake. There is no proxy, no such thing. I just tried it in chromium and saw 'Red Hat Enterprise Linux Test Page' and I did not believe that by default httpd on RHEL6 returns 403.

Note You need to log in before you can comment on or make changes to this bug.