As long as the request is processed through IIS (i.e.
http://yoursitename/yourpage.html) then this will work. it doesn't matter
whether it's coming through a proxy or not. As far as IIS is concerned, it's
a HTTP request.
If you are accessing a page by double-cliking on it in Explorer or similar,
then it's not being processed by IIS, and no server-side processing is done.
The only other way that i can think of to describe what you might be seeing
is that there are actually two websites, and the proxy is directing requests
to one site, and directly accessing the URL is going to a different
(misconfigured) IIS site.
Cheers
Ken
"AndyK" <AndyK.DeleteThis@discussions.microsoft.com> wrote in message
news:DD2EEAFD-0361-4DA2-A0CC-0073ABEAD322@microsoft.com...
> We are currently mapping both the .html and .html extension through
> asp.dll
> this appears to work fine when the server is accessed through a proxy
> server.
> When accessed from the console or from an outside ISP the .html or .htm
> files
> do not process the asp instructions or the server side include files, they
> return them to the client. This does not occur with files with a .asp
> extension.
>
> The server is Windows Server 2000 SP 4 running IIS 5.0 (Our web host
> assures
> me that it patched up to date)
>
> Can anybody think of a reason why it would work with a proxy byt fail
> without? and better yet... can anybody think of a way to fix it?
>
> Thanks