Closed
Bug 444663
Opened 16 years ago
Closed 16 years ago
ssl_error_rx_record_too_long
Categories
(Core :: Security: PSM, defect)
Tracking
()
RESOLVED
INVALID
People
(Reporter: mailinglistsacc, Assigned: KaiE)
Details
User-Agent: Mozilla/5.0 (X11; U; Linux i686; de; rv:1.9) Gecko/2008061800 (Gentoo) Firefox/3.0 Build Identifier: Mozilla/5.0 (X11; U; Linux i686; de; rv:1.9) Gecko/2008061800 (Gentoo) Firefox/3.0 i am trying to use ampache and playback does not work because of this error: ssl_error_rx_record_too_long opera f.e. works flawless firefox does not work. no matter whether linux or windows Reproducible: Always Steps to Reproduce: 1.visit website 2.playback 3.fail and aids
Updated•16 years ago
|
Assignee: nobody → kaie
Component: General → Security: PSM
Product: Firefox → Core
QA Contact: general → psm
Version: unspecified → 1.9.0 Branch
Comment 1•16 years ago
|
||
This is most likely plain text over https. Try to access the site via regular http on port 443. Please resolve the bug if this is the case.
Reporter | ||
Comment 2•16 years ago
|
||
http://mysite.tld:443 brings this: 400 Bad Request Your browser sent a request that this server could not understand. Reason: You're speaking plain HTTP to an SSL-enabled server port. Instead use the HTTPS scheme to access this URL, please. the link that was fetched by ampache had http://bla.tld:80 my webserver changed that to https://bla.tld:80 thus complaining about the connection. so it wasnt plain text over https but https over the plain text port ^^ thnx for your time :)
Status: UNCONFIRMED → RESOLVED
Closed: 16 years ago
Resolution: --- → FIXED
Comment 3•16 years ago
|
||
nothing changed in the Mozilla source code and that means that this bug can not be resolved as fixed. marking invalid
Resolution: FIXED → INVALID
Comment 4•2 years ago
|
||
Hello, a few tips to solve this problem:
- Clear history and cache data (please note that you may be logged out of the web pages you logged in to).
- Check that you have updated Firefox to the latest version.
- Try using HTTP protocol instead of HTTPS.
- Start firefox in Troubleshoot Mode (https://mzl.la/3vUhzHB)
Hope this helps
You need to log in
before you can comment on or make changes to this bug.
Description
•