User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:22.214.171.124) Gecko/20061204 Firefox/126.96.36.199 Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:188.8.131.52) Gecko/20061204 Firefox/184.108.40.206 I can't go to the log in page for my web mail account now that I have Firefox 220.127.116.11 on mu iMac computer Reproducible: Always Steps to Reproduce: 1.I go to nwoca.org home page 2.click on web mail button 3. can't open to log in page for the web mail. 4. process worked before i downloaded Firefox 18.104.22.168 yesterday onto my iMac Actual Results: I receive this message: This address uses a network port which is normally used for purposes other than Web browsing. Firefox has canceled the request for your protection. Clicking the "try again" button changes nothing. Expected Results: I would go to the sign in page for my mail. I can do this if I use a another computer or window explorer. I could do this before I downloaded Firefox 22.214.171.124 yesterday afternoon.
Yeah, I see this too on a seamonkey branch build. This is because we now, for security reasons, block access to port 563. So this bug is probably invalid. Someone should probably contact the webmaster of the site. Not sure if it's common to set up webmail access via port 563...
Assignee: nobody → dveditz
Component: File Handling → Security
Product: Firefox → Core
QA Contact: file.handling → toolkit
Version: unspecified → 1.8 Branch
The SSL ports of standard mail services were added to the blocked list with bug 301762 last July. It did not change in 126.96.36.199, you must have been several critical bug-fix releases behind if you're just now hitting the problem (I think 188.8.131.52 was the first one with this fix in it, or SeaMonkey 1.0.5). Port 563 is the standard port for SSL NNTP services. Ports lower than 1024 are reserved for standard services and should not be used for other things, such as web sites. If you cannot get your service provider to correct their error you can add port 563 individually to the override list in your prefs. See http://www.mozilla.org/projects/netlib/PortBanning.html and if you need help contact one of the community support groups listed at http://www.mozilla.org/support/#community (real-time chat might be fastest)
Status: UNCONFIRMED → RESOLVED
Last Resolved: 12 years ago
Resolution: --- → INVALID
My bad, it didn't go into any 1.5 release, just Firefox 2 and SeaMonkey 1.1
You need to log in before you can comment on or make changes to this bug.