Intriguing Problem Mapping HTML to ASP

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

Re: Intriguing Problem Mapping HTML to ASP

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" 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

Re: Intriguing Problem Mapping HTML to ASP

We actually tracked it down to the compression settings in IIS, with them
switched off it started working. It seems that it was compressing the stream
before processing it as ASP and sending the unprocessed text to the client.

Thanks Anyway.

"Ken Schaefer" wrote:

> 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" 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
>
>

Re: Intriguing Problem Mapping HTML to ASP

No - that shouldn't have any effect. Something else is up.

It may be that the files were compressed prior to you mapping the extension
to ASP? And cached versions were being delivered to your browser?

Cheers
Ken


"AndyK" wrote in message
news:37BC2098-87BB-4288-92E6-B9F7DD57564C@microsoft.com...
> We actually tracked it down to the compression settings in IIS, with them
> switched off it started working. It seems that it was compressing the
> stream
> before processing it as ASP and sending the unprocessed text to the
> client.
>
> Thanks Anyway.
>
> "Ken Schaefer" wrote:
>
>> 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" 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
>>
>>

Re: Intriguing Problem Mapping HTML to ASP

We tried clearing the cache but that had no effect. But, leaving application
compression on and switching static compression off did work. I also
replecated this in an environment that had never used compression. Now
knowing what I'm looking for I found that static compression and application
compression take their file extension list from the metabase not from
applications mapping screen.

http://www.microsoft.com/technet/prodtechnol/windows2000serv /technologies/iis/maintain/featusability/httpcomp.mspx



"Ken Schaefer" wrote:

> No - that shouldn't have any effect. Something else is up.
>
> It may be that the files were compressed prior to you mapping the extension
> to ASP? And cached versions were being delivered to your browser?
>
> Cheers
> Ken
>
>
> "AndyK" wrote in message
> news:37BC2098-87BB-4288-92E6-B9F7DD57564C@microsoft.com...
> > We actually tracked it down to the compression settings in IIS, with them
> > switched off it started working. It seems that it was compressing the
> > stream
> > before processing it as ASP and sending the unprocessed text to the
> > client.
> >
> > Thanks Anyway.
> >
> > "Ken Schaefer" wrote:
> >
> >> 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" 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
> >>
> >>
>
>