IE6 won't open named anchor ('href=#xx') if file ext isn't HTML

[Guest]

Using IE6 for XP. I'm testing local web pages and can't get IE to open link
to a named anchor if the anchor is in a file with any extension except HTML
or HTM (such as .ASP, or other exts mapped to type "HTML Document"). For
example,
A HREF="Abc.asp#xyz" .... from any file, or
A HREF="#xyz" .... from within .ASP or other non-HTML file
It just displays a blank white page. BTW, the named anchors aren't empty.

It isn't only ASP. I created a brand new ext (.ASQ) of type "HTML Document"
and copied reg values from HKCR\.html, but it had same problem as ASP.

Note these cases DO work:
- Use 'Open in New Window' (context menu) works fine, even for ASP file.
- Simply rename the (target) file extension to HTML, then it works.
- Use Firefox to open any anchor in any file, new or same window, works fine.

Ran Process Monitor which shows that for ASP file, it thinks the anchor is
part of the filename, i.e., looks for a file named 'C:/Abc.asp#xyz' and
fails. For HTML file, it looks for correct name, 'C:/Abc.html' without the
#xyz.

One thing I noticed - I don't have a 'URL: File protocol' listed under
'Folder Options...File Types', and my HKCR\file key has a "URL protocol"
value but its data is empty. Would this matter?

 

[Jon Kennedy]

For a better, faster response to this issue, post to the appropriate forum
here:
http://forums.asp.net/ That's where you'll find the web page coding gurus.

This newsgroup is for users having issues with IE, and isn't really for web
page coding issues per se.

 

[Guest]

Thanks, Jon, I do appreciate your suggestion, but it isn't a coding or asp
issue. It's an issue of why IE parses file URLs differently for html
extension, than it does for other extensions also of type "HTML Document".
I have no asp code, just simple basic html. Anyway, the fact that simply
changing the file extension fixes the problem, proves it isn't the code. And
creating a brand new extension (.asq) which also breaks, proves .ASP isn't
the culprit.

I'm pretty sure it's just a minor registry tweak I just don't know where.
Maybe the missing "URL: File protocol"... ?