Novell BorderManager SSL authentication page shows HTML source code




14 years ago
13 years ago


(Reporter: ColinPearce, Assigned: Blake Ross)


Firefox Tracking Flags

(Not tracked)




14 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.6) Gecko/20050225 Firefox/1.0.1
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.6) Gecko/20050225 Firefox/1.0.1

My preferred text editor, which I use to edit HTML files (UltraEdit32)
automatically detects the file type when the file is loaded. It will look for
the FF FE marker for Unicode files and I found that it was prepending UTF-8
files with this marker were it not present. 

Therefore when I customize the BMLogin page, even simple text changes, this file
marker was added at the start of the file. Normally this has no effect, but when
the page is served by the BorderManager mini webserver and viewed with the
firefox browser, things broke ie. HTML source code is displayed. IE displays the
page fine.

If I make the edits in Notepad or DOS Edit then the custom page works fine.
Because the Unicode file marker is not added to the file.

Reproducible: Always

Steps to Reproduce:
1.Customize the BorderManager login page using UltraEdit32 or use any HTML file
that has the Unicode file marker (FF FE)
2.Attempt to authenticat to the proxy server using Firefox
3.HTML source code of the BMLogin page is displayed

Actual Results:  
HTML source code of the BMLogin page is displayed and authentication is not

Expected Results:  
Authentication page should be displayed

This problem is specific to an interaction between the Novell BorderManager mini
web server and the Firefox browser and as such has a very limited scope.
This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Last Resolved: 13 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.