Sitecore: Site resolver issue with similar domains

I faced an issue with Sitecore Site resolver with similar domain (hostName).

If there are two different websites with similar domain (www.example.com and www.example.com.pl), Sitecore resolves the site based on the order of site node in the web.config (or SiteConfiguration.config in includes folder).

Configuration: (Not Working)

Order 1: <site hostName=”www.example.com” …

Order 2: <site hostName=”www.example.com.pl” …

Sitecore resolves to www.example.com even though we browse www.example.com.pl.

--------------------------------

Configuration: (Working)

Order 1: <site hostName=”www.example.com.pl” …

Order 2: <site hostName=”www.example.com” …

Here, order has been changed to COM.PL first and Sitecore resolves properly for both the domains – www.example.com, www.example.com.pl

Is it a Sitecore site resolver issue or is it an expected behavior?

Sitecore support ticket has been created – 408068. Waiting for their inputs… J

Sitecore: Reset Sitecore admin account password to default

Sitecore administrator might have forgotten the admin password.
If you would like to reset it to default, you can follow the below steps. Password will be reset to ‘b’.

In Sitecore Core DB, you can run this attached SQL script and this will reset the password to ‘b’.

Hope this helps!!! 

Sitecore – IIS Output Cache – Handler doesn’t return proper data.

Recently we migrated our website to Sitecore.NET 6.6.0 (rev. 130529). We have a custom handler (.ashx) to pull data from database in JSON format. We experienced Inconsistency in the response while executing handler. It worked for first two times and later it just responded with last response and request was not even hitting Sitecore. IIS Output caching (User-mode or Kernel-mode output caching in IIS) itself sent the cached response.

Later we came to know that IIS output caching is not supported officially by Sitecore – Sitecore doesn’t support ASP.NET Output Caching.