Thanks for your response.
The AllowPathInfoForScriptMapping has not been set for the exact reason you
have specified. I don't want to change that for obvious reasons. I'll ask
the people on site today if they have anything running on that machine that
might interfere with normal operations. We already looked for ISAPI filters
and didn't find any, but we'll look again. There's always the possibility of
overlooking something.
Is there some type of configuration besides the "Check if File Exists" that
could cause this problem? In fact that flag doesn't perfectly replicate the
issue since it doesn't even allow non-extension extended path info to exist.
E.G. <a style='text-decoration: underline;' href="http://www.url.com/path/script.aspx/report?id=200" target="_blank">http://www.url.com/path/script.aspx/report?id=200</a> would not work if
that flag is set while currently, it works in that way. The only type of URL
structure that doesn't work has the extension, such as:
<a style='text-decoration: underline;' href="http://www.url.com/path/script.aspx/report.ext?id=200" target="_blank">http://www.url.com/path/script.aspx/report.ext?id=200</a> (where "script.aspx"
is the script page and "/report.ext" is just extended path info).
Thanks again!
Bri Gipson
----- Original Message -----
From: "David Wang [Msft]" <someone.TakeThisOut@online.microsoft.com>
Newsgroups: microsoft.public.inetserver.iis
Sent: Tuesday, May 25, 2004 2:47 AM
Subject: Re: PATH_TRANSLATED / SCRIPT_NAME server variable 404 issue.
> AllowPathInfoForScriptMapping will need to be left as default ( 0 ) if you
> want ASP/ASP.Net to function. Setting it to 1 will definitely cause
> ASP/ASP.Net to not function -- if you say that you set it to 1 and
> ASP/ASP.Net is still working, then either that configuration is not taking
> effect (perhaps overridden at a lower level by the same setting), or
> something ELSE is going on with your server, outside of IIS, that is
> affecting behavior.
>
> Do you happen have URLScan running on the failing server such that it is
> rejecting the .ext extension ?
>
> I tried out a test ASP.Net page on my Windows 2000 Server, and I had it
> function properly with with /vdir/script.aspx/path.info?query with
default
> AllowPathInfoForScriptMapping value and on the root and vdir. So, I think
> you have something else running on this particular IIS server that is
> changing server behavior -- start looking at applicable ISAPI Filters at
the
> global and site level.
>
> --
> //David
> IIS
> This posting is provided "AS IS" with no warranties, and confers no
rights.
> //<!-- ~MESSAGE_AFTER~ -->
>> Stay informed about: PATH_TRANSLATED / SCRIPT_NAME server variable 404 issue.