Closed Bug 361816 Opened 18 years ago Closed 18 years ago

url encoding (e.g. www.%67oogle.com/) non-functional

Categories

(Core :: General, defect)

defect
Not set
normal

Tracking

()

RESOLVED DUPLICATE of bug 309671

People

(Reporter: piratepenguin, Unassigned)

References

()

Details

User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9a1) Gecko/20061119 Minefield/3.0a1 Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9a1) Gecko/20061119 Minefield/3.0a1 If Opera and IE7 got it right, http://www.%67oogle.com/ should = http://www.google.com/ http://www.google.com/ appears in the status bar when http://www.%67oogle.com/ is highlighted, however when you click it "Firefox can't find the server at www.%67oogle.com", so this is inconsistent. Reproducible: Always Steps to Reproduce: 1.visit http://www.%67oogle.com/ 2. 3. Actual Results: "Firefox can't find the server at www.%67oogle.com" Expected Results: google.com opens
As far as I know, %-encoding is not valid for hostnames, so I think this is INVALID.
Product: Firefox → Core
QA Contact: general → general
Version: unspecified → Trunk
Indeed, RFC 2396 forbids percent-encoding in hostnames.
Status: UNCONFIRMED → RESOLVED
Closed: 18 years ago
Resolution: --- → INVALID
(In reply to comment #2) > Indeed, RFC 2396 forbids percent-encoding in hostnames. > So, should we do anything about the status bar? Thanks.
Blocks: 361817
Blocks: 361818
Blocks: 361819
if an app shows the wrong thing in the status bar, it earns a bug. i filed 3 :).
Status: RESOLVED → VERIFIED
sorry, you guys are wrong. RFC 3986 obsoletes 2396 and allows escaped hostnames. furthermore, this is a duplicate.
Status: VERIFIED → UNCONFIRMED
Resolution: INVALID → ---
*** This bug has been marked as a duplicate of 309671 ***
No longer blocks: 361817, 361818, 361819
Status: UNCONFIRMED → RESOLVED
Closed: 18 years ago18 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.