This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
This bug prevent the users browsing HTML files of Usersguide as all the files have .htm extension instead of .html
To allow support for "*.htm" files (which are bogus names, IMHO), added AddType text/html .htm to httpd.conf.
This is not fixed because although the extensions may have been fixed in the webserver conf, the source browser does not know about them (and I think the issue is with the source browser, not regular web pages). For example: http://usersguide.netbeans.org/source/browse/~checkout~/usersguide/javahelp/org/netbeans/modules/usersguide/appd18.htm This URL displays the file as plain text. It should show HTML (as it does if you append ?content-type=text/html to the URL), but the source browsing script does not recognize the MIME type correctly. I'm not sure if source browse URLs for the usersguide are currently being linked to or not. BTW I agree that *.htm is not a desirable extension, however that is what typical Windows-based apps like the one that created the usersguide generate, so we have to live with it and treat it as text/html. Can the source browse script be made to share MIME type configuration with the general site webserver?
Isn't this the intent for source browsing? When I browse HTML source code, I expect to see the source code to the HTML, not the interpreted page. Is this not the way that source browsing is supposed to work?
Got it. HTML displays interpreted but HTM displays as text. Bummer. Looking into it.
I believe that this has been resolved -- this was done by making it use the mime.types which is referenced by httpd.conf. I'm marking it fixed -- if it is, please mark it closed ... otherwise, please reopen. The link shown below doesn't work -- apparently because this file is now in the Attic. But other files I tested (eg. xml files) now offer the possibility of download w/ the content type specified in mime.types. If you see any problems, please let me know.
Cannot verify the fix due to #9313.
We recently moved out from Collabnet's infrastructure