Serving everything over https causes an even greater slowdown on satellite internet connections such as Hughesnet or WildBlue, as the provider-side optimizations used to cope with the high latency don't function at all with https. As a result, Launchpad is slower on satellite than it is on dial-up due to the use of https everywhere - which has been a MAJOR issue for me when testing Ubuntu's unstable distribution (as I have a satellite connection). This in a way discourages me from reporting bugs - and has me thinking of switching to and testing Debian, who doesn't have an HTTPS-only bug tracker.
Is it possible to switch to using https for the password only, or at least offer this as an option? Those of us on high-latency and low-bandwidth connections would especially appreciate it, as the status quo makes using launchpad an unpleasant experience. I'd really like to hear from the devs on this, as I'm effected greatly by this right now.
Serving everything over https causes an even greater slowdown on satellite internet connections such as Hughesnet or WildBlue, as the provider-side optimizations used to cope with the high latency don't function at all with https. As a result, Launchpad is slower on satellite than it is on dial-up due to the use of https everywhere - which has been a MAJOR issue for me when testing Ubuntu's unstable distribution (as I have a satellite connection). This in a way discourages me from reporting bugs - and has me thinking of switching to and testing Debian, who doesn't have an HTTPS-only bug tracker.
Is it possible to switch to using https for the password only, or at least offer this as an option? Those of us on high-latency and low-bandwidth connections would especially appreciate it, as the status quo makes using launchpad an unpleasant experience. I'd really like to hear from the devs on this, as I'm effected greatly by this right now.