286124 - When editing auto-completion result, correct protocol not inserted

Status: RESOLVED DUPLICATE of bug 239684

(Firefox :: Address Bar, defect)

Description

[Christian Hudon]

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.5) Gecko/20050210 Firefox/1.0 (Debian package 1.0+dfsg.1-6)
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.5) Gecko/20050210 Firefox/1.0 (Debian package 1.0+dfsg.1-6)

I have a couple of web sites accessible only through https. Sometimes I'll
access pages of these websites by typing the start of the web address in the
location bar, selecting one of the entries that's close enough to the URL I
want, editing the end of the url to get exactly the url I want to go, and then
pressing enter. 

This almost works. I'll get a page that says access denied, or somesuch because
when firefox inserted the auto-completed URL into the location bar, it didn't
put the https prefix, and then when I pressed enter, it used the default method
of http: to access the site.

Reproducible: Always

Steps to Reproduce:
1. Visit a couple of pages on an https: website to populate the browser's history.
2. In a new tab/window, hit Ctrl-L to go to the location bar
3. Type the beginning of the hostname for the website you browsed in step 1
4. Select one of the entries offered in the auto-completion by pressing
down-arrow a couple of times
5. Edit the entry by, say, pressing backspace to erase the last component of the
URL. (foo.example.com/abc/def/ -> foo.example.com/abc/)
6. Press enter to go to the edited url
Actual Results:  
You end up at http://foo.example.com/abc/

Expected Results:  
Get you to https://foo.example.com/abc/

Comment 1

[Mark Byers]

I think this is a duplicate of bug 239684.

Comment 2

[Gervase Markham [:gerv]]

This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/

Comment 3

[Christian Hudon]

Yes, this bug is still reproductible with the latest version of firefox (1.5
beta1). It's very easy to reproduce too, if only someone who reads this could
take the time (and mark it as confirmed). If my description of the steps to
reproduce the bug isn't clear, ask and I'll be happy to explain further.

Comment 4

[John Vandenberg]

*** This bug has been marked as a duplicate of 239684 ***