As for the error:
The message received from the server could not be parsed. Common causes
for this error are when the response is modified by calls to
response.Write(), response filters, HttpModules, or server trace is
enabled. Details: Error parsed near ' <!DOCTYPE html P'.
We have no idea about it. You mentioned that it is thrown occasionally, but yet, are you able to provide some basic steps to reproduce it? We did a quick search for this error, but didn't find anything related to the Sitefinity.
As for accessing the CMS pages without extensions, yes, currently it is allowed by the CmsHttpModule. Actually, this filter is left for the higher level, i.e. IIS mappings. However, this setting are not applicable to the IIS 7 with intergrated pipeline mode
, where all requests are handled by the ASP.NET application. Is this your case? Please look at the article: http://learn.iis.net/page.aspx/508/wildcard-script-mapping-and-iis-7-integrated-pipeline/
Maybe you are right, we should consider an option to deny extensionless URLs in the CmsHttpModule. We will discuss it for the next release.
In the meantime, you can use on of the following approaches:
- Switch the IIS 7 mode to classic;
- Create an HttpModule, which redirects the extensionless URLs, and place it on the top of the http modules collection.
the Telerik team
, the state of the art learning tool for Telerik products.