Thread: URL Rewrite error V9 removed c- p-

In V9 I have my URL Rewrite setup so I remove c- , p- and am hosting on Server 2008.

<add name="Product" url="{SEName}-{ProductID}.html" virtualPath="~/showproduct.aspx" checkPhysicalUrlAccess="false" />

<add name="Category" url="{SEName}-{CategoryID}.aspx" virtualPath="~/showcategory.aspx" checkPhysicalUrlAccess="false" />

Note products rewrite to html and categories to aspx

My issue is, to do this I believe html has to be set on the server to run through the aspx engine so the page gets rendered properly. Once this happens regular html like pageerror.html needs to run through the same engine and breaks.

If I change the html page for products to aspx the site seems to get confused whether category links are products or categories and sends my category links to product pages.

My goal is to get static html working in the root again but I really want to keep my product and category URL's:

racecars-166.aspx for my categories
blue-car-mag-wheels-turbo-graphics-456.html for products

I have decided the html vs. aspx is irrelevant but I don't want to return to p- or c-.

Anyone have an idea if this can be fixed or is aspdnsf not going to like it without the prefix in some way.

MSD

A simple solution might be to process ".html" through .net and keep ".htm" out of .net. This way you can keep your static pages for errors and the like and just have them use ".htm".

As far as getting the rewrites to work correctly in ASPDNSF I can't be much help. I have always kept the url structure unmodified.

Chaz.

I guess the next obvious question is how does the application differentiate between:

{SEName}-{ProductID}.aspx
{SEName}-{CategoryID}.aspx

Can a URL be constructed this way or will the ID not know if its a Category because we pulled the c- and p- out. I think I am slowly figuring out I just can't remove the c- because the software can't differentiate the category call from a product call. I made it work with an html for products and an aspx for categories but if I want them to be both aspx it does not like it.

MSD