Forcing https on a public site is bad

| | Comments (0) | TrackBacks (0)

I'm currently at work and I try to access bugzilla.mozilla.org. I can't because my proxy only lets me access known secure sites (meaning a handfull support sites, banks and that's it). I don't know who got the idea of making bugzilla a secure site by forcing ssl connections to it. The problem des not come from my dns or anything else because I've got review request stating that the protocol be https.
Besised me being pissed-off and unable to reach bugzilla from work, what's the point of having all bugzilla being ssled, this will slow it down badly because the server will have to encrypt all coonectiosn to the site. IT will securise the login/password I agree but it should be kept an option for people like me behind firewall and proxies.

0 TrackBacks

Listed below are links to blogs that reference this entry: Forcing https on a public site is bad.

TrackBack URL for this entry: http://perso.hirlimann.net/cgi-bin/mt/mt-tb.cgi/756

Leave a comment

Technorati

Technorati search

» Blogs that link here

About this Entry

This page contains a single entry by ludo published on 23 septembre 2004 9h02.

Inscrit ! was the previous entry in this blog.

Windows update, spyware etc .. is the next entry in this blog.

Find recent content on the main index or look in the archives to find all content.

Pages

View Ludovic Hirlimann's profile on LinkedIn
www.flickr.com
Powered by Movable Type 4.1