Closed
Bug 71441
Opened 25 years ago
Closed 25 years ago
Server-relative URLs with protocol specifier handled incorrectly
Categories
(SeaMonkey :: General, defect)
Tracking
(Not tracked)
People
(Reporter: owain, Assigned: asa)
References
()
Details
From Bugzilla Helper:
User-Agent: Mozilla/4.75 (Macintosh; U; PPC)
BuildID: 2001030808
A URL of the form http:/directory/file is handled as if it
was http://server/file
Reproducible: Always
Steps to Reproduce:
1. Place a URL of the form http:/directory/file as an anchor or form action
2. Go to the page and activate the link
Actual Results: The browser interpreted the directory part as a server name and
attempted to contact it.
Expected Results: The URL should have been interpreted as a request relative to
the current server.
dupe of verified invalid bug, please dupeme.
Keywords: qawanted
Whiteboard: DUPEME
Comment 2•25 years ago
|
||
Duplicate of (WONTFIX) 32966. See the discussion there and in RFC 2396.
32966 probably rates a mostfreq by now.
| Reporter | ||
Comment 3•25 years ago
|
||
RFC 2396 sez:
Some parsers allow the scheme name to be present in a relative URI if
it is the same as the base URI scheme. This is considered to be a
loophole in prior specifications of partial URI [RFC1630]. Its use
should be avoided.
http:g = http:g ; for validating parsers
| http://a/b/c/g ; for backwards compatibility
Isn't backwards compatibility a Good Thing?
sometimes.
*** This bug has been marked as a duplicate of 32966 ***
Status: UNCONFIRMED → RESOLVED
Closed: 25 years ago
Keywords: qawanted
Resolution: --- → DUPLICATE
Whiteboard: DUPEME
Updated•21 years ago
|
Product: Browser → Seamonkey
You need to log in
before you can comment on or make changes to this bug.
Description
•