Thank you for your input and alternative suggestions.
>Each location can only specify one URL. If you need more you need multiple location entries.
>
>There are a few ways you can deal with this:
>
>Put all unauthenticated items into a single folder (maybe the root and all authenticated in subfolders) then use that for the location that's not authenticated.
>
>Another way you can do this is skip the Forms Authentication configuration section and explicitly check for authentication on your pages. It's pretty trivial to write code to check if a user is authenticated and if not redirect them to your login page of choice. You can write a single static method in a helper class that that does that and call it from each request (or even a page base class if most cases require it and then have a flag to not authenticate).
>
>+++ Rick ---
>
>>Hi,
>>
>>When using Form Authentication you can specify in the web.config that an ASPX page should be allowed for any user without authentication.
>>This is a sample code:
>>
>>
>><location path="MyTestPage1.aspx">
>> <system.web>
>> <authorization>
>> <allow users ="*" />
>> </authorization>
>> </system.web>
>></location>
>>
>>
>>And you can have as many of these Location specified as needed. But I was wondering if it is possible to specify multiple aspx pages in one location. Here is what I tried but it does not work:
>>
>>
>><location path="MyTestPage1.aspx; MyTestPage2.apx; MyTestPage3.aspx">
>> <system.web>
>> <authorization>
>> <allow users ="*" />
>> </authorization>
>> </system.web>
>></location>
>>
>>
>>Please let me know if it is possible and how. TIA
"The creative process is nothing but a series of crises." Isaac Bashevis Singer
"My experience is that as soon as people are old enough to know better, they don't know anything at all." Oscar Wilde
"If a nation values anything more than freedom, it will lose its freedom; and the irony of it is that if it is comfort or money that it values more, it will lose that too." W.Somerset Maugham