[atlas] Forcing https in Atlas
- Previous message (by thread): [atlas] Forcing https in Atlas
- Next message (by thread): [atlas] RIPE Atlas roadmap, September 2012 version
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Richard Barnes
rbarnes at bbn.com
Tue Oct 16 18:42:46 CEST 2012
See also: <http://tools.ietf.org/html/draft-ietf-websec-strict-transport-sec-14> <http://en.wikipedia.org/wiki/HTTP_Strict_Transport_Security> On Oct 4, 2012, at 5:14 AM, Robert Kisteleki wrote: > Dear Atlas users, > > At the moment the Atlas UI servers allow regular, unsecured (http) > connections from clients. For particular features, most notably anything > that requires authenticated users, we're using secure (https) connections. > Unfortunately, the potential mixing of the two schemes causes glitches and > inconsistencies for some users. > > Therefore on 15 October we will start enforcing secure connections towards > the Atlas UI servers (atlas.ripe.net and *.atlas.ripe.net). We'll do this by > automatically redirecting all http queries to their https equivalents. > > This should not cause any changes to those of you who already use https by > default, and should not cause any notable changes to anyone else. However, > some clients (especially CLI based ones) may need some extra flags to deal > with https connections. > > Regards, > Robert Kisteleki >
- Previous message (by thread): [atlas] Forcing https in Atlas
- Next message (by thread): [atlas] RIPE Atlas roadmap, September 2012 version
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]