If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

URL convertion: scheme;foo to scheme:foo

RESOLVED EXPIRED

Status

SeaMonkey
Location Bar
P5
enhancement
RESOLVED EXPIRED
16 years ago
8 years ago

People

(Reporter: Jeremy M. Dolan, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

16 years ago
scheme;foo URLs can be often typed in by mistiming 'shift' and ';' for the ':'.
RFC 1738 lists ';' as a character reserved for use in the scheme-specific part
of the URL. This means it's invalid in the scheme part, and we can safely assume
a ':' was meant.

Currently, ftp;//site.com loads http://www.ftp.com/ (thanks to stupid .com
autoguessing), which redirects to some company that bought them.

Updated

16 years ago
OS: Linux → All
Hardware: PC → All

Updated

16 years ago
Priority: -- → P5
Target Milestone: --- → Future
(Reporter)

Comment 1

16 years ago
If you can point me to the URL clean up code, I can make an attempt. Should be
little work/risk for a decent reward.

Comment 2

15 years ago
moving neeti's futured bugs for triaging.
Assignee: neeti → new-network-bugs

Comment 3

15 years ago
-> URL bar
Assignee: new-network-bugs → hewitt
Component: Networking → URL Bar
QA Contact: benc → claudius

Comment 4

14 years ago
We aren't going to support a lot of overly-clever fixup in the URL bar code
anymore. 

Feel free to do this via internet keywords :)
Assignee: hewitt → location-bar
QA Contact: claudius
Product: Core → SeaMonkey

Comment 5

8 years ago
MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614
Status: NEW → UNCONFIRMED

Comment 6

8 years ago
MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but still has no comment since the inception of the SeaMonkey project 5 years ago.

Because of this, we're resolving the bug as EXPIRED.

If you still can reproduce the bug on SeaMonkey 2 or otherwise think it's still valid, please REOPEN it and if it is a platform or toolkit issue, move it to the according component.

Query tag for this change: EXPIRED-20100420
Status: UNCONFIRMED → RESOLVED
Last Resolved: 8 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.