Re: foo.example.com
Re: foo.example.com
- Subject: Re: foo.example.com
- From: Douglas Norton <email@hidden>
- Date: Thu, 3 Mar 2005 15:33:32 +0000
Tim,
I saw this at my previous company.
It happened when the cgi processing had bailed for some reason and this
is defined as the cgi failure page in one of the standard setup files
(http.conf ??).
Anyway, resetting the web service always fixed this.
On the actual server log there would be messages about insufficient
resources to launch the cgi handler.
So,
1) restarting the web service is probably a good idea, as you are
already doing.
&
2) fixing the setup so that it fails to a page on the relevant website
with a 'Sorry there is a problem, come back later' message wold also be
a good idea.
Hope this helps
Douglas.
On 3 Mar 2005, at 15:09, Timothy Larkin wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
I have a simple application that keeps track of whether a specific web
server is operating correctly. It does this by requesting a certain
page from the server and examining the result for a specific string.
If the response from the server does not contain the string, then my
application sends a signal to the server computer to restart the web
service.
My application also generates a log. If there is a problem with the
response, then the log contains an entry like this, " Invalid response
to connection (<NSURLConnection
http://10.236.78.22:16080/fmi/iwp/res/iwp_home.html>).", where
"10.236.78.22" is the IP address of the host, and the string between
"<" and ">" is generated by the "@%" format directive on the
NSURLConnection object.
However, I see frequent occurrences of an odd log entry in which the
NSURLConnection object describes itself as "<NSURLConnection
http://foo.example.com/cgi-bin/tester>". I don't know what
"foo.example.com" can possibly refer to. I have determined that
"foo.example.com" is a commonly used generic name in Unix network
documentation. But I cannot understand why, or under what
circumstances, the connection description should appear in this form,
and whether this indicates a problem with my code, or is simply some
bizarre bug in the NSURLConnection description code.
Tim Larkin
Cornell University
-----BEGIN PGP SIGNATURE-----
Version: PGP 8.0.3
iQA/AwUBQicotjs3LpUOUjFkEQKpjQCgu0k+2admy8pOn1gjutqWA2lSedEAnjED
fM/yjSy+Dwq1/hbV2Z3epZP+
=+ah7
-----END PGP SIGNATURE-----
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
email@hidden
This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden