viewing text files over internet
am 05.04.2006 17:48:38 von Jon Phipps
first off my appologies if this is OT for this group.
I have an odd situtation on my hands under Server 2k3 standard. I have a
password protected site set up which basically allows readonly access to all
drives and folders on the server machine. This is all well and good, except
for when I go to view a text or log file then the server returns 404 object
not found even though I am looking right at the file. I have the permissions
set up as no script access, read, directory browsing allowed. I have
allowed(under ntfs) read access to all the users that need it as well as
IUSR_SERVER. Yet still the same error, it does not matter if I set up the
log files folders as separate virtual folders, use webfolders or how I set
things up I cannot get this to work.
TIA
Jon
Re: viewing text files over internet
am 05.04.2006 20:18:12 von IISMVP2005
Check your IIS log file and see if you are getting a SubStatus of 3 which
means that there is no MIME type for this file.
You did not indicate the type of file extension of these text files.
404.3-MIME Map Policy Prevents This Request
If a request is denied because a MIME map restriction is in effect, a 404.3
error is returned. When substatus logging is enabled, if you look at this
request in the IIS logs, you will see an entry similar to the following:
2002-11-25 05:46:27 127.0.0.1 GET /somefile.unkext - 80 - 127.0.0.1 - 404 3
50As with a 404.2 error, a 404.3 error causes a Win32 error to be logged. In
this case, the error is 50, which is an ERROR_NOT_SUPPORTED error.
Another quick way to verify that a MIME map restriction is in effect is to
add a wildcard MIME type to the virtual directory in question. This enables
all MIME types to be served without restriction. Then, repeat the failed
HTTP request and verify that it is served successfully.
Adding a wildcard MIME type to the virtual directory is a troubleshooting
step, not a solution to the problem. Leaving the wildcard in place and
allowing all MIME types to be served compromises the security of the server.
For more information about adding a wildcard MIME type, see
http://www.microsoft.com/technet/prodtechnol/WindowsServer20 03/Library/IIS/eb5556e2-f6e1-4871-b9ca-b8cf6f9c8134.mspx
--
Cheers
Chris Crowe [IIS MVP 1997 -> 2006]
http://blog.crowe.co.nz
------------------------------------------------
"Jon Phipps" wrote in message
news:OTXAohMWGHA.128@TK2MSFTNGP05.phx.gbl...
> first off my appologies if this is OT for this group.
>
>
>
> I have an odd situtation on my hands under Server 2k3 standard. I have a
> password protected site set up which basically allows readonly access to
> all drives and folders on the server machine. This is all well and good,
> except for when I go to view a text or log file then the server returns
> 404 object not found even though I am looking right at the file. I have
> the permissions set up as no script access, read, directory browsing
> allowed. I have allowed(under ntfs) read access to all the users that need
> it as well as IUSR_SERVER. Yet still the same error, it does not matter if
> I set up the log files folders as separate virtual folders, use webfolders
> or how I set things up I cannot get this to work.
>
> TIA
> Jon
>