We have a homepage in our MOSS 2007  pages library (http://domain.com.au/pages/home.aspx). This page is has anonymous access enabled and is accessible to our public users.

We have developed a new homepage design which is a custom application name. We want to keep the url for this new page the same as the old one in the pages library (http://domain.com.au/pages/home.aspx)

 

what we did is create a new SPSolution and add this part to elements.xml.

<Module Name="RWSPHomePage" Url="Pages" Path="Pages" >
    <File  Url="HomePage.aspx" />
  </Module> 

Now the problem is, when we deploy our new solution and try to access the new page via the specified url  it then prompts the user to login.

My guess is it’s doing this because of the url. When the user types the url to the application page (http://domain.com.au/pages/home.aspx), sharepoint thinks they want to access the pages library which needs specific permission to be seen by users.

 

I have changed the aspx file name to homepage2.aspx but still same result.

 

Is there any trick that sharepoint doesn't think of pages library and use the pages name in element file first. This would enable us to use the new application page, without having to change the url from that of our old homepage in the pages library.