The logs should be written in UTF-8 which shouldn't be a problem. I don't know what would cause that. Are you setting the CCSID somewhere in your config file to something else?

Matt

-----Original Message-----
From: web400-bounces@xxxxxxxxxxxx [mailto:web400-bounces@xxxxxxxxxxxx] On Behalf Of Terry Anderson
Sent: Friday, August 31, 2007 3:10 PM
To: web400@xxxxxxxxxxxx
Subject: Re: [WEB400] CGIDEV2 & Page not Found.

Matt,
Thanks for the reply.

When I look at the log, through either the wrklnk command or WordPad, all I see is the following garbage:
[Fri Aug 31 09:41:42 2007] [error] [client 10.39.239.9] éâÙåmÔâÇððñøz@Ɖ“…@l¢@„–…¢@•–£@…§‰¢£

Do you know a way to convert this to something readable?

Terry Anderson



message: 6
date: Fri, 31 Aug 2007 11:38:13 -0400
from: <matt.haas@xxxxxxxxxxx>
subject: Re: [WEB400] CGIDEV2 & Page not Found.

Terry,

The HTTP error log will tell you what's being called. This
sounds like a problem with your httpd.conf file. When the
server doesn't know how to fulfill a request, you'll get
entries like this in the error log:

[Fri Aug 31 11:23:12 2007] [error] [client 64.107.94.17]
ZSRV_MSG0018: File /tltswebs/serviceplus/favicon.ico does
not exist [Fri Aug 31 11:23:12 2007] [error] [client
64.107.94.17] ZSRV_MSG0016: URI in request GET /favicon.ico
HTTP/1.1 is not valid

The first entry is what it tried to resolve the request to
and the second is the URI (URL less the protocol and host
name) that was requested.

If the error log doesn't help, you could always start the
server with option -vv (two lowercase V's), try the page,
and stop the server. This will produce a trace log that will
show you what's going on.

Matt


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.