Closed
Bug 92747
Opened 24 years ago
Closed 12 years ago
URL - http: with @ in request (HTTP error 404)
Categories
(Core :: Networking, defect, P2)
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: grampp, Unassigned)
References
()
Details
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:0.9.2+)
Gecko/20010729
BuildID: 2001072908
Mozilla cannot find an URL that contains "@" (see URL field!). Mozilla
transposes '@' to Hex %40 after entering the URL - but this should work as well.
Reproducible: Always
Steps to Reproduce:
1.enter URL
2.
3.
Expected Results: show existing page
Comment 1•24 years ago
|
||
Hmm. This is interesting. There is no need for us to escape the @, since it is
not reserved in this part of the uri. But rfc2616, section 3.2.3, says:
"Characters other than those in the "reserved" and "unsafe" sets (see RFC 2396
[42]) are equivalent to their ""%" HEX HEX" encoding."
Now, @ is in the reserved set in rfc2396, but section 2.2 of that says that:
"Characters in the "reserved" set are not reserved in all contexts. The set of
characters actually reserved within any given URI component is defined by that
component. In general, a character is reserved if the semantics of the URI
changes if the character is replaced with its escaped US-ASCII encoding."
Section 3.3 of that spec has grammar allowing escaped characters in the path.
However, since either behaviour is correct, we should do what ns4 and
(presumably) ie do, and not escape it.
So I don't think that we're doing anything wrong, but we probably shouldn't be
escaping, for compatability.
darin? benc? comments?
If someone types a URL from a user-entry point, I think we should escape it.
If an author posts something (links in page), my general take is to transmit in
a way the current browsers do this.
I've only red up to RFC 1738, so I am listening to anyone that quotes a newer
document...
Comment 4•23 years ago
|
||
investigating for 0.9.6, this works fine from NS 4.75 (tested under linux).
i think we should strive for compatibility in this case since the spec would
permit it.
Status: NEW → ASSIGNED
Priority: -- → P2
Target Milestone: --- → mozilla0.9.6
summary more consistent w/ other summaries now...
Summary: HTTP URLs with @ sign cannot be found (HTTP error 404) → URL - http: with @ in request (HTTP error 404)
Comment 7•23 years ago
|
||
not critical for mozilla1.0
-> future
Target Milestone: mozilla0.9.8 → Future
The url is no longer valid. I tried to google for other sites with "@" in the
url, but I couldn't find one that easy...
Anyone has another example?
Comment 9•19 years ago
|
||
-> default owner
Assignee: darin → nobody
Status: ASSIGNED → NEW
Component: Networking: HTTP → Networking
QA Contact: benc → networking
Target Milestone: Future → ---
Comment 10•12 years ago
|
||
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•