Re: Auto-selection of secure protocol

I do agree that this would be a good thing to implement, though there is one
issue with this. Checking an adress to be available as https takes time (as
it takes time for pinging a adres that does not exists), so loading the page
is delayed by a second or so. This issue can be removed by having a
whitelist of sites that have an https, though that one needs to be
maintained.

Secondly I think that it is the operator of the site that needs factor in
the need for a secure connection. Even though that may be the case, we would
always have a choice for certain sites. Wouldn't it make more sense to
implement this in an addon? However that would make us use the secure
connection, not the novice...

Eddie.

On Mon, Oct 13, 2008 at 11:01 AM, Guillaume Michaud <[email protected]>wrote:

> Maybe we could have the following beheviour :
>
> - Case 1 : HTTP and HTTPS website
> The user types "myurl" ; the browser redirects him to "http://myurl" ;
> then,
> in the background, it checks wether the website is available in HTTPS ; it
> finds out it is, so a pop-up asks the user if he wants to switch to the
> secure version or not (and can remember this choice for later connexions).
>
> - Case 2 : HTTP-only website
> The user types "myurl" ; the browser redirects him to "http://myurl" ;
> then,
> in the background, it checks wether the website is available in HTTPS, but
> it is not ; it does nothing, and everything's ok.
>
> - Case 3 : HTTPS-only website
> The user types "myurl" ; the browser tries to redirects him to "
> http://myurl"
> ; when the connection times out, it tries to redirect him to "
> https://myurl"
> ; it works, and everything's ok. The browser could remember that too for
> later connexions.
> _______________________________________________
> wishlist mailing list
> [email protected]
> https://lists.mozilla.org/listinfo/wishlist
>