After a bunch of more scares from viruses, they may have done something to the configuration of our work network so that this no longer works.
This is what I used to see in my access log when things were working:
mywork.place.org - - [15/Jun/2003:17:02:47 -0400] "GET /MyPage/ HTTP/1.0" 401 469
mywork.place.org - fido [15/Jun/2003:17:02:52 -0400] "GET /MyPage/ HTTP/1.0" 200 1115
mywork.place.org - fido [15/Jun/2003:17:02:57 -0400] "GET /MyPage/send_it.cgi HTTP/1.0" 302 255
mywork.place.org - - [15/Jun/2003:17:02:57 -0400] "GET / HTTP/1.0" 200 1201
It worked like this. Client requests a page (MyPage). This page is password protected. Client supplies password for user fido. MyPage is served up. Client executes a cgi script on the MyPage page (send_it.cgi), and good things happened.
Here is what I seen now.
209.55.73.244- - [03/Oct/2003:08:47:19 -0400] "GET /MyPage/ HTTP/1.0" 401 469
209.55.73.244- fido [03/Oct/2003:08:47:27 -0400] "GET /MyPage/ HTTP/1.0" 200 1115
209.55.73.244- fido [03/Oct/2003:08:47:37 -0400] "GET /MyPage/send_it.cgi HTTP/1.0" 302 255
209.55.73.244- - [03/Oct/2003:08:53:08 -0400] "-" 408 -
There are two differences in these logs. First, my workplace ip no longer resolves. That is, nslookup 209.55.72.244 is unsuccessful. This ip can be pinged, however. The second is the error code, 408, which means request timed out. So, I am guessing that apache is trying to resolve the canonical name of my work ip, failing to do this, and timing out. It doesn't execute the cgi script. I have HostnameLookups Off but I do have Use CanonicalName On
The httpd.conf says the following:
# UseCanonicalName: (new for 1.3) With this setting turned on, whenever # Apache needs to construct a self-referencing URL (a URL that refers back # to the server the response is coming from) it will use ServerName and # Port to form a "canonical" name. With this setting off, Apache will # use the hostname:port that the client supplied, when possible. This # also affects SERVER_NAME and SERVER_PORT in CGI scripts. #
This is unclear to me. It looks like the documentation is using "server" and "client" to both refer to the remote computer. This has me confused. I don't know if the Canonical Name is the name of the server (my apache box at home) or the client at work. Does this mean that apache will identify itself by whatever name the client provided to it? That seems to make the most sense. If so, this shouldn't be influencing my problem.
I don't use SERVER_NAME or SERVER_PORT in my cgi scripts although I do use REMOTE_ADDR and REMOTE_USER.
This is a hard problem to troubleshoot since I have to be at work to test this but I can only makes change to my server while at home. This really slows down trouble shooting.
I have changed UseCanonicalName to Off, and in a few days (today is Fri.) I will find out if this solves the problem. Meanwhile, any suggestions appreciated.
BTW, all the names and addresses in the body of the letter are bogus, changed to protect the innocent from the not so innocent.
Joel
_______________________________________________ Linux-users mailing list [EMAIL PROTECTED] Unsubscribe/Suspend/Etc -> http://smtp.linux-sxs.org/mailman/listinfo/linux-users
