Are you using URLScan or some other ISAPI filter on IIS? This can register
a 404 error if the request for the file is rejected for any reason (e.g.
permissions) because a filter can't utilize custom errors.
What program does windows say .log is associated with?
IIS basically has three common types of 404:
(a) a file extension that is not registered with IIS, disabled in IIS, or
not associated with a mime type. You can see the mime types in Control
Panel > Administrative Tools > IIS Manager, right-click the server name, hit
Properties, and click on the MIME Types... button. .log isn't listed on my
server by default, so unless you've explicitly listed it and something else
is going wrong, you will likely resolve your error by hitting New... and
adding .log with a MIME type of text/plain (if you want the browser to
display the .log file directly) or application/octet-stream if you want them
to be prompted to open it (which will open the file in the program *their*
system is registered to read .log files with) or save it to disk.
(b) the file really isn't there...
(c) the oddball rare error I mentioned above.
HTH
On 3/1/05 11:25 PM, in article
2F**********************************@microsoft.com, "MarkP"
<Ma***@discussions.microsoft.com> wrote:
Is there a workaround to allow .log files to be accessed
Like: http://127.0.0.1/Test.log
The access is just so it can be downloaded.
I get 404 errors for Windows 2003 but not for Windows 2000 for this.
