Hi, On Mon, Mar 24, 2014 at 02:27:39PM +0100, Denis Walker wrote:
The RIPE Database release 1.72 has now been fully deployed to production.
We would like to point out that, with this release, Webupdates and Syncupdates can only be accessed with HTTPS and not with HTTP. This is to conform to the requirements of using RIPE ACCESS now as an authentication method for updating the RIPE Database. Any update using HTTP will be automatically redirected to HTTPS.
Uh, what? This does not *exactly* meet POLA, and that part of the change was not announced as such - and as it's quite likely that this breaks someone's syncupdate script (why would a syncupdate client be written to handle http->https redirects if all it wants is a single POST?) this really should have been announced before. ... and I'm less than convinced that wanting to have HTTPS *for RIPE ACCESS* is a good reason to force it by surprise on everyone else. Gert Doering -- NetMaster -- have you enabled IPv6 on something today...? SpaceNet AG Vorstand: Sebastian v. Bomhard Joseph-Dollinger-Bogen 14 Aufsichtsratsvors.: A. Grundner-Culemann D-80807 Muenchen HRB: 136055 (AG Muenchen) Tel: +49 (0)89/32356-444 USt-IdNr.: DE813185279