This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/db-wg@ripe.net/

[db-wg] [ncc-services-wg] Fwd: RIPE Database Release 1.72 - including SSO Integration

Previous message (by thread): [db-wg] Fwd: RIPE Database Release 1.72 - including SSO Integration
Next message (by thread): [db-wg] Fwd: RIPE Database Release 1.72 - including SSO Integration

Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Sander Steffann sander at steffann.nl
Mon Mar 24 23:26:14 CET 2014

Hi,

> 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.

I fully agree. Making https mandatory for updates is a change in the public interface to the DB and it should have been announced.

Denis: can you gather some stats on how many POSTs are sent over http, get a redirect, and then don't retry over https? It would give a rough estimate of how many scripts can't handle the redirect.

Cheers,
Sander

Previous message (by thread): [db-wg] Fwd: RIPE Database Release 1.72 - including SSO Integration
Next message (by thread): [db-wg] Fwd: RIPE Database Release 1.72 - including SSO Integration

Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

[ db-wg Archives ]