Any reason not to have all pages .aspx?

Even if most are HTML only?

[Wlauzon]

We are redoing our site on an ASP.NET server. For now at least, only a few pages actually use asp - most are just pure html.

So is there any reason not to make all pages with the aspx suffix, even if they are plain vanilla?

[icantthinkofone]

I can't think of any except some people may try and access you site by typeing www.yoursite.com/index.html so make sure your server responds to that.

[RonPK]

I can imagine some server overhead as all .aspx pages are parsed by the ASP parser. Also, timestamps will probably always show the current time, not the last-modified time.

[oxbaker]

if your doing anythign with sessions or tracking clicks, logging sessions (in anything other than the IIS log files) its a good idea to have the pages .aspx, at least with that you can quickly insert some tracking functions into the page_load event. While it WILL take a bit longer to load an .aspx file the difference (if your web server is up to snuff) will be unnoticable. The majority of my pages are aspx, but we still do use .html pages for stiff like Privacy Policies, or Rules & Regs, just static stuff. The only real benefit of converting them to aspx is the ability to easily extend them if you need to in the future.

hth,
mcm

[skipfactor]

>>you can quickly insert some tracking functions

You can also quickly insert a 301 via asp.