[db-wg] call for application authorisation ideas

Hi All

I stand corrected :)


On 24/08/2015 11:23, denis wrote:
> Hi Gert and others
>
> On 22/08/2015 22:37, Gert Doering wrote:
>> Hi,
>>
>> On Thu, Aug 20, 2015 at 11:19:34PM +0200, Job Snijders wrote:
>>> On Thu, Aug 20, 2015 at 10:24:20PM +0200, Gert Doering wrote:
>>>> c) syncupdates - works with PGP-signed objects
>>>
>>> Mmmm interesting, you just POST against
>>> https://apps.db.ripe.net/syncupdates/simple-rpsl.html?
>>
>> The script I downloaded from RIPE about a decade ago seems to post
>> to
>>     http://syncupdates.db.ripe.net/
>>
>
>
> This is an ancient URL that still works because it is redirected to the
> apps.db.ripe.net address. I was never a great fan of keeping old URLs
> alive indefinitely and maintaining a mass of redirects. If one of these
> redirects gets dropped accidentally during some system upgrade or
> maintenance a service suddenly fails for many users. The apps URL has
> been around now for a few years. Users should be advised to change to it
> and a time limit given for when old URLs are dropped from service.

The http://syncupdates.db.ripe.net/ is still a valid URL for scripts to 
use whereas https://apps.db.ripe.net/syncupdates/simple-rpsl.html is a 
web form for end users to use. But my argument still stands that there 
are some redirects still in use and these should have a time limit.

cheers
denis

>
> cheers
> denis
>