Re: HTML file server side includes plus forms authentication
- From: "William F. Zachmann" <wfz@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Mon, 24 Oct 2005 21:15:11 -0400
Alex,
Thanks for your intention to help however, if you read through my original
message, you will see that I have already considered the possibility of
simply re-naming the htm/html files with aspx extensions but that this is
not a very good option since the old (massive) C++ dll has many hard-coded
dependencies tied to the file (and, for that matter, directory) names. I
quite explicitly said that I was looking for another alternative.
All the best,
will
"Alex" <Alex@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:7CA1CE05-59A9-4107-BCAF-8675AB75E4BE@xxxxxxxxxxxxxxxx
> Will,
>
> how about this:
> 1. Rename your .html files to .aspx
> 2. For the .html hyperlinks generated by your DLL you write an HTTP
> Handler
> that does an URL rewrite from .html to .aspx.
> For example this is what happens when you click on
> http://www.dotnet42.com/NG_microsoft.public.dotnet.framework.drawing/A_605/T
> hreadDetail.htm
>
>
> Alex
>
> http://www.DotNet42.com - The Answer to Your DotNet Question
>
>
> "William F. Zachmann" wrote:
>
>> We've got a project going that involves moving an old web site with a
>> massive dll written in C++ that produces most of the output from a SQL
>> 7.0
>> data base on NT4 onto IIS on Windows 2003 Server with SQL 2000. All new
>> code is being written in C# using ASP.NET and we are using forms
>> authentication to control access to particular directories/applications.
>>
>> We are having a hard time figuring out how to configure the thing so that
>> existing html files both a) have access controlled through ASP.NET forms
>> authentication and b) render server side includes correctly. If we
>> configure the htm/html files for the application on IIS to be handled by
>> ssinc.dll the includes are rendered correctly, but access is not
>> restricted
>> by forms authentication. If we configure them to be handled by
>> aspnet_isapi.dll we get forms authentication control, but the includes
>> are
>> ignored.
>>
>> Oddly, simply renaming a file from *.html to *.aspx with no other changes
>> results in aspnet_isapi.dll handling it correctly -- providing forms
>> authentication access control and also rendering includes correctly. But
>> if
>> the file name is *.htm or *.html, aspnet_isapi.dll fails to include the
>> includes. It almost seems like this is a bug! I cannot, at any rate,
>> see
>> any reason why it would do this by design.
>>
>> So, in theory, we could solve the problem by just re-naming all our
>> htm/html
>> files with an aspx extension instead. Unfortunately this is not so
>> easily
>> done in practice since the old C++ .dll that creates most pages and fills
>> them with stuff from the data base has hyperlinks to the *.html files
>> hard
>> coded into it all over the place. It is not impossible to change this,
>> but
>> we'd like to find a simpler way.
>>
>> Can anyone offer a suggestion for a way to resolve this problem? Is it
>> simply a bug that aspnet_isapi.dll renders includes for *.aspx files but
>> fails to do so for an otherwise identical files with a .htm or .html
>> extension?
>>
>> All the best,
>>
>> will
>>
>> William F. Zachmann, President
>> Canopus Research Inc.
>> http://www.canopusresearch.com
>>
>>
>>
.
- References:
- HTML file server side includes plus forms authentication
- From: William F. Zachmann
- RE: HTML file server side includes plus forms authentication
- From: Alex
- HTML file server side includes plus forms authentication
- Prev by Date: Re: IE not displaying aspx but firefox is?
- Next by Date: Re: HTML file server side includes plus forms authentication
- Previous by thread: RE: HTML file server side includes plus forms authentication
- Next by thread: Re: HTML file server side includes plus forms authentication
- Index(es):
Relevant Pages
|
