I don't think it's a timeout problem.

I can go to the website just fine via a browser window.

A ping test shows fast transmission time.

I've put the Test output below.

It's only doing this on two servers, but on every URL

on the server.

James

Tue Nov 7 12:46:20 2006: Not Found

Date: Tue, 07 Nov

red http://myhost.mydomain.com:8068/SELoginAccess.jsp - Not Found Date: Tue, 07 Nov

HTTP/1.1 404 Not Found Date: Tue, 07 Nov 2006 18:46:25 GMT Server: IBM_HTTP_Server/2.0.47 Apache/2.0.47 (Unix) DAV/2 Content-Length: 332 Connection: close Content-Type: text/html; charset=iso-8859-1

Seconds: 0.09

If you copy the exact URL to your desktop and you can get '200 ok' or alike, then you maybe hitting the wrong server from Hobbit. Do you have HOSTS entry for 'myhost.myodmain.com' point to one IP on your test box, but don't have it on your Hobbit server, or vice versa? Or they use different DNS servers?

To be sure and for troubleshooting, you can always add '=10.1.3.4' after the port number.

http://myhost.mydomain.com:8068/SELoginAccess.jsp

On 11/7/06, Hubbard, Greg L <greg.hubbard at eds.com> wrote:

Wonder why the Web server is giving you a 404? Is there some sort of redirection going on, or is the Web server disallowing access to certain IP addresses?

GLH

---

*From:* James Wade [mailto:jkwade at futurefrontiers.com] *Sent:* Tuesday, November 07, 2006 12:53 PM *To:* hobbit at hswn.dk *Subject:* RE: [hobbit] HTTP Red

I don't think it's a timeout problem.

I can go to the website just fine via a browser window.

A ping test shows fast transmission time.

I've put the Test output below.

It's only doing this on two servers, but on every URL

on the server.

James *Tue Nov 7 12:46:20 2006: Not Found *

Date: Tue, 07 Nov

[image: red] http://myhost.mydomain.com:8068/SELoginAccess.jsp - Not Found

Date: Tue, 07 Nov

HTTP/1.1 404 Not Found

Date: Tue, 07 Nov 2006 18:46:25 GMT

Server: IBM_HTTP_Server/2.0.47 Apache/2.0.47 (Unix) DAV/2

Content-Length: 332

Connection: close

Content-Type: text/html; charset=iso-8859-1

Seconds: 0.09

I am not aware of any differences, and I am not enough of a Web-head to understand all this, but what my untrained eyes see are:

a) Hobbit is getting a 404 from the Web server, which means that the URL was not right, or for some reason the Web server didn't want to serve up the file.

b) The file being requested is a jsp -- not sure that this would throw a wrench in anything. I believe Henrik has probably been asked to support jsp retrievals by now.

Unless Henrik can provide some pointers, I would be tempted to "sniff" the connection between the Hobbit server and this Web server to see what is really being exchanged...

GLH

From: James Wade [mailto:jkwade at futurefrontiers.com] 
Sent: Tuesday, November 07, 2006 1:37 PM
To: hobbit at hswn.dk
Subject: RE: [hobbit] HTTP Red



I switched over from Big Brother to Hobbit. The History shows

the

URL's working just fine until I switched over to Hobbit. Does

Hobbit

monitor URL's differently than Big Brother?

 

Here's the same URL from BB this morning:

 

http://myhost.mydomain.com:8068/SELoginAccess.jsp - Server OK
HTTP/1.1 200 OK
Date: Mon, 06 Nov 2006 21:41:18 GMT
Server: IBM_HTTP_Server/2.0.47 Apache/2.0.47 (Unix) DAV/2
Set-Cookie:

JSESSIONID=0000EYsgo4Q0FwZBBl6Ro8ZaQZ9:11ascfppf_Path=/ Cache-Control: no-cache="set-cookie,set-cookie2" Expires: Thu, 01 Dec 1994 16:00:00 GMT Connection: close Content-Type: text/html_ charset=iso-8859-1 Content-Language: en-US Seconds: 0.06

From: Hubbard, Greg L [mailto:greg.hubbard at EDS.COM] 
Sent: Tuesday, November 07, 2006 1:03 PM
To: hobbit at hswn.dk
Subject: RE: [hobbit] HTTP Red

 

Wonder why the Web server is giving you a 404?  Is there some

sort of redirection going on, or is the Web server disallowing access to certain IP addresses?

GLH

	 

	

	From: James Wade [mailto:jkwade at futurefrontiers.com] 
	Sent: Tuesday, November 07, 2006 12:53 PM
	To: hobbit at hswn.dk
	Subject: RE: [hobbit] HTTP Red

	I don't think it's a timeout problem.

	I can go to the website just fine via a browser window.

	A ping test shows fast transmission time.

	I've put the Test output below.

	 

	It's only doing this on two servers, but on every URL

	on the server. 

	 

	James


	Tue Nov 7 12:46:20 2006: Not Found 

	Date: Tue, 07 Nov 
	 
	  http://myhost.mydomain.com:8068/SELoginAccess.jsp -

Not Found Date: Tue, 07 Nov HTTP/1.1 404 Not Found Date: Tue, 07 Nov 2006 18:46:25 GMT Server: IBM_HTTP_Server/2.0.47 Apache/2.0.47 (Unix) DAV/2 Content-Length: 332 Connection: close Content-Type: text/html; charset=iso-8859-1 Seconds: 0.09

I have a lot cont= checks in my bb-hosts against .jsp. so, I don't think it is .jsp offending anybody. I guess you could check your web server log to check what the server mapped it too when the test failed with them JSP in the chekc.

One of mine: cont=http://mydomain.com/tester1.jsp;okeydokey

On 11/7/06, James Wade <jkwade at futurefrontiers.com> wrote:

O.K., I took out the .jsp and they work now.

Weird the way the other .jsp's work. I wonder if it's

something strange on the install of the two servers.

Basically I took out all the SELoginAccess.jsp:

http://myhost.mydomain.com:8068

As soon as I did everything went green.

Henrik, Any idea what I can look for on the .jsp side

that would cause it to fail?

Thanks for the help. Mentioning it might be the .jsp did the trick.

James

---

*From:* Hubbard, Greg L [mailto:greg.hubbard at eds.com] *Sent:* Tuesday, November 07, 2006 1:50 PM *To:* hobbit at hswn.dk *Subject:* RE: [hobbit] HTTP Red

I am not aware of any differences, and I am not enough of a Web-head to understand all this, but what my untrained eyes see are:

a) Hobbit is getting a 404 from the Web server, which means that the URL was not right, or for some reason the Web server didn't want to serve up the file.

b) The file being requested is a jsp -- not sure that this would throw a wrench in anything. I believe Henrik has probably been asked to support jsp retrievals by now.

Unless Henrik can provide some pointers, I would be tempted to "sniff" the connection between the Hobbit server and this Web server to see what is really being exchanged...

GLH

---

*From:* James Wade [mailto:jkwade at futurefrontiers.com] *Sent:* Tuesday, November 07, 2006 1:37 PM *To:* hobbit at hswn.dk *Subject:* RE: [hobbit] HTTP Red

I switched over from Big Brother to Hobbit. The History shows the

URL's working just fine until I switched over to Hobbit. Does Hobbit

monitor URL's differently than Big Brother?

Here's the same URL from BB this morning:

http://myhost.mydomain.com:8068/SELoginAccess.jsp - Server OK

HTTP/1.1 200 OK

Date: Mon, 06 Nov 2006 21:41:18 GMT

Server: IBM_HTTP_Server/2.0.47 Apache/2.0.47 (Unix) DAV/2

Set-Cookie: JSESSIONID=0000EYsgo4Q0FwZBBl6Ro8ZaQZ9:11ascfppf_Path=/

Cache-Control: no-cache="set-cookie,set-cookie2"

Expires: Thu, 01 Dec 1994 16:00:00 GMT

Connection: close

Content-Type: text/html_ charset=iso-8859-1

Content-Language: en-US

Seconds: 0.06

---

*From:* Hubbard, Greg L [mailto:greg.hubbard at EDS.COM] *Sent:* Tuesday, November 07, 2006 1:03 PM *To:* hobbit at hswn.dk *Subject:* RE: [hobbit] HTTP Red

Wonder why the Web server is giving you a 404? Is there some sort of redirection going on, or is the Web server disallowing access to certain IP addresses?

GLH

---

*From:* James Wade [mailto:jkwade at futurefrontiers.com] *Sent:* Tuesday, November 07, 2006 12:53 PM *To:* hobbit at hswn.dk *Subject:* RE: [hobbit] HTTP Red

I don't think it's a timeout problem.

I can go to the website just fine via a browser window.

A ping test shows fast transmission time.

I've put the Test output below.

It's only doing this on two servers, but on every URL

on the server.

James *Tue Nov 7 12:46:20 2006: Not Found *

Date: Tue, 07 Nov

[image: red] http://myhost.mydomain.com:8068/SELoginAccess.jsp - Not Found

Date: Tue, 07 Nov

HTTP/1.1 404 Not Found

Date: Tue, 07 Nov 2006 18:46:25 GMT

Server: IBM_HTTP_Server/2.0.47 Apache/2.0.47 (Unix) DAV/2

Content-Length: 332

Connection: close

Content-Type: text/html; charset=iso-8859-1

Seconds: 0.09

On Tue, Nov 07, 2006 at 01:50:07PM -0600, Hubbard, Greg L wrote:

a) Hobbit is getting a 404 from the Web server, which means that the URL was not right, or for some reason the Web server didn't want to serve up the file.

Right. One possible explanation - especially when dynamic webpages are involved - is that the JSP checks for the "User-Agent" header it gets from the browser, or in this case from Hobbit's network tester. E.g. this is often done to accomodate incompatibilities between Internet Explorer and the rest of the world in how they interpret HTML.

BB sends a HEAD request like this:

HEAD /SELoginAccess.jsp HTTP/1.0 User-Agent: BigBrother/1.9c Host: myhost.mydomain.com:8068

Hobbit sends a GET request like this:

GET /SELoginAccess.jsp HTTP/1.1 Connection: close Host: myhost.mydomain.com User-Agent: Hobbit bbtest-net/4.2.0 Accept: */* Pragma: no-cache

which should be much more like a "normal" browser request. I dont think the HTTP 1.0/1.1 difference matters, but you *can* ask Hobbit to use HTTP 1.0 by defining the URL with "http10" as in

1.2.3.4 myhost # http10://myhost/SELoginAccess.jsp

The only other difference is that BB includes the port number in the "Host:" header. I haven't noticed that before. I've just checked the HTTP 1.1 RFC, and it's true that the "Host" header must include the port number if it is not the default (80 for http, 443 for https). You may want to try the attached patch to see if it makes a difference.

It would also be interesting to see what the webserver logs as the reason for generating a 404 status.

b) The file being requested is a jsp -- not sure that this would throw a wrench in anything. I believe Henrik has probably been asked to support jsp retrievals by now.

This is handled entirely by the webserver. As long as it's an HTTP request, Hobbit doesn't care what kind of data is being requested.

Regards, Henrik