716608 - Not Valid URL (https://www.mydomain.tld:8080) [SSL on specified port]

Status: RESOLVED WORKSFORME

(Core :: Networking, defect)

Description

[bug]

User Agent: Mozilla/5.0 (Windows NT 5.1; rv:9.0.1) Gecko/20100101 Firefox/9.0.1
Build ID: 20111220165912

Steps to reproduce:

This looks like the same issue as Bug 624353, however, that was a long time ago for a totally different version of FireFox.  I have never run into this bug and have been using Firefox for a very very long time.  Only saw this bug today using the most current FireFox 9.0.1, so perhaps the bug has been re-introduced--hence the new post.

In that bug they talked about self-signed certificates, and I suppose any site I have tried and gotten the error also is a self-signed certificate.  I don't get the error on any SSL site that doesn't need a specified port--but any that I can think of would also not be self-signed.  So, I don't know if the bug is because of the self-signed certificate, or if it is the specified port, or a combination of the two.


Actual results:

When I attempt to load any of my secure remote admin pages for various domains using the URL format: https://www.mydomain.tld:8080, instead of receiving any warnings or being taken to the web page, I get a popup "alert" box saying "The URL is not valid and cannot be loaded."

For security, I am not releasing my websites, and my ports on which the remote admin is active, however, this would be easily reproducible with any out-of-the-box install of WebMin on any Linux flavor.


Expected results:

A warning regarding the self-signed certificate and the choice to continue to the website, AND/OR usually in FireFox just a message box asking if I want to accept the certificate exception (permanently or just for the session), and then continuing to the website once I have accepted the certificate.

Comment 1

[bug]

Ooops, the paragraph "For security..." should have been under Steps to reproduce:

Sorry for my first time posting errors.  Also, this is FireFox on Windows XP platform.

Comment 2

[mjl]

i've got the same issue.
this is a fresh windows xp pro sp3 installation, with firefox 3.6.25 and firefox 9.0.1.
i use multiple profiles.
if i run ff3 on a profile, and open a https-url with invalid ssl certs (eg self-signed), i get the normal "cannot be trusted" warnings.
if i do the same with ff9 on the same profile, i get the popup box saying "This URL is not valid and cannot be loaded.".
if i whitelist the cert/domain (not sure what is important there) using ff3 permanently, switch to ff9 on the same profile, i can view the domain just fine.
using ff3 to whitelist your cert/domain seems to be a workaround for now.

it seems more people are seeing this error:
http://support.mozilla.org/en-US/questions/912499

Comment 3

[bug]

I don't use "profiles" at all, and I only have FF9 installed.  I tried a completely clean install of FF9 (first uninstalling, and deleting ALL registry keys associated with FF, before reinstalled) and I still get the problem.  Not sure if it is related, but I have noticed another bug that annoys me very much.  I do use the setting to "never remember history" but have found that it still remembers different history.  For example, it keeps me logged into some websites, and it doesn't refresh other website pictures (that change daily).  I now have to go in and manually hit "clear all current history" for it to really clear the history (that it isn't supposed to be remembering).

As soon as I am less busy I plan to go back to an earlier version of firefox.  Incidentally, having almost the exact same build (same make model of PC, same OS, same install procedures, etc.) for my computer at home, and when FireFox auto-updated to 9.0.1 Neither problem shows up there.

Makes me really confused as to what is going on.

Comment 4

[Wayne Mery (:wsmwk)]

Do you still see this when using a current version?
(If you do not, please close this bug as WORKSFORME or INVALID)

Comment 5

[bug]

(In reply to Wayne Mery (:wsmwk, use Needinfo for questions) from comment #4)
> Do you still see this when using a current version?
> (If you do not, please close this bug as WORKSFORME or INVALID)

Wow, does BugZilla automatically flag, for review, bug reports coming up on four year anniversary?  Or, was this just happenstance you looked at this one yesterday? Rhetorical questions no need to reply.   I had totally forgotten reporting this bug; totally forgotten even running into it.  I had to read my detailed notes to even remember having filed it.  Yep is certainly my style of writing (and it does spark my memory to some degree).  Though, I can't say if I figured out a work around, or just went back to an earlier version of FF for a time until upgrading to one that didn't have the bug; but certainly must have continued somehow as I still use WebMin nearly daily.

Following my line of thoughts, this WORKSEFORME_NOW, as I currently get the expected Untrusted Connection message for self signed certificates (now I even know how to create my own, and if I still had such a problem could have identified if it had to do with specific ports, or just the certs themselves, self-signed only, or self-signed and not FQDN matched, or a combination); with the option to Add an Exception and then after doing so I can continue on to the website.

I do have to add the exception every time (not a bother to me, easy couple of expected clicks); as it does not give the option to permanently save the exception (grayed out box); but I presume that is because I still always use private browsing option (never remembering history).  Not remembering history is just one manner in which I keep the computer very clean, absolutely necessary to be able to continue to functionally and productively use a P4 with Win XP still to this day.  (On that thought my second note on this mentioned an issue with saving history when told not to; and I have not seen that for a long time either.)

Although I am loosing faith in FireFox, many websites no longer work at all under XP with FireFox even the latest version, but do work with Google Chrome (though have also run into some that don't run at all with either under XP).  I presume such websites use out-of-the-box-javascript-frameworks that no longer support XP, and no longer even test under XP.  So, despite FireFox updating and still installing on XP, it's getting less relevant to me each day.

Someday, maybe, should the stars perfectly align, and the economy improve enough for my employers; and/or someone with more money is willing to hire this crazy old man; I will be able to upgrade to a modern OS as well.

Been a loyal FireFox user since I heard of it near the beginning of the Second Browser Wars... by all accounts Google Chrome is now the winning party; and I must test my web sites with it... (or are we already at the Third Browser Wars?)  On a side note, ran into almost identical bug in Google Chrome but dealing with Certs for a DNS-based web filter, figured out the cert had to be installed as a "Trusted Root Source" rather than put in any other collection, gives me all sorts of thoughts as to how I would troubleshoot this bug if I were to see it today.

But, as I don't currently have this problem, I am marking this status as resolved and worksforme.