Carlos,

I agree with the statement that you will be hitting the same portal regardless of which URL you enter in this case.  I didn't meant to imply that you could customize settings based on the alias being used, but rather that the browser itself would think of the two sites as being completely different, and may have cached the pages temporarily for one of the URLs.  In that scenario, one would potentially see two of the same pages configured differently , even though its the same portal (as the browser has the page cached for a particular URL).

However, I don't think setting the modules cachetime would make any difference in this scenario (as I thought it would earlier) -- as that is completely different from the browser keeping a cached version of a page or site.

Take care,

Ian

Hi Ian and Carlos,

I was busy in site completion and also I didn't get the notification of your replies so did not update this.

I have checked the code and knew that module settings are stored in cache using HttpRunTime.Cache and HttpRunTime.cache uses Temporary ASP.NET files for this.

The issue was that as my portal has to aliases www.domainname.com and www.domainname.co.nz and for IIS it’s two different web sites and because of this “Temporary ASP.NET files” folder contains two separate folders for each site. So when user request site www.domainname.com, module settings would be cached in folder of domainname.com and when user request site www.domainname.co.nz, module settings is stored in domainname.co.nz folder.

So when I change the module settings value from domaniname.com, cache of domainname.com is updated so it works fine but who will update the cache stored in domainname.co.nz folder.

I think there is only one way to resolve this is call Config.touch() method as it clears the cache of both folder.

Thanks,
Ruchir
 

Hi,

Thanks for pointing out this two points. Now we both are on the same page.