status-check redirects to itself?
Since today, status-check seems to redirect to itself? % curl -v https://atlas.ripe.net/api/v2/measurements/2060427/status-check\?permitted_total_alerts=3 ... < HTTP/1.1 301 Moved Permanently < Server: nginx/1.16.1 < Date: Wed, 29 Apr 2020 17:57:17 GMT < Content-Type: text/html; charset=utf-8 < Content-Length: 0 < Connection: keep-alive < Location: /api/v2/measurements/2060427/status-check/?permitted_total_alerts=3 What's up?
On 2020/04/29 19:58 , Stephane Bortzmeyer wrote:
Since today, status-check seems to redirect to itself?
% curl -v https://atlas.ripe.net/api/v2/measurements/2060427/status-check\?permitted_total_alerts=3
< Location: /api/v2/measurements/2060427/status-check/?permitted_total_alerts=3
Note the backward slash and the forward slash. The redirect is to a slightly different URL.
On Wed, Apr 29, 2020 at 08:05:18PM +0200, Philip Homburg <philip.homburg@ripe.net> wrote a message of 10 lines which said:
The redirect is to a slightly different URL.
OK, thanks, I did not notice the detail. But it worked before (I use it in a monitoring script), and the behavior changed somewhere around 29 april, 13:20 UTC.
Hi, On Thu, Apr 30, 2020 at 08:25:26AM +0200, Stephane Bortzmeyer wrote:
The redirect is to a slightly different URL.
OK, thanks, I did not notice the detail. But it worked before (I use it in a monitoring script), and the behavior changed somewhere around 29 april, 13:20 UTC.
Same behaviour here. The fix is easy enough but it would be nice to be warned when API endpoints change, or did I miss something? Cheers, Benjamin -- Benjamin Collet
On 2020-04-30 08:50, Benjamin Collet wrote:
Hi,
On Thu, Apr 30, 2020 at 08:25:26AM +0200, Stephane Bortzmeyer wrote:
The redirect is to a slightly different URL.
OK, thanks, I did not notice the detail. But it worked before (I use it in a monitoring script), and the behavior changed somewhere around 29 april, 13:20 UTC.
Same behaviour here. The fix is easy enough but it would be nice to be warned when API endpoints change, or did I miss something?
Hello, We deployed some changes around the date Stephane mentioned. This was not intended to affect the URL behaviour, and we're investigating why this is happening. We'll get back to you soon. In the meantime: api/xxx/?parameters (ie. with a slash at the end of the URL before the potential parameters) works as intended so you can use this form, at least for now. Regards, Robert
Hi all, As Robert mentioned, this change was unintentional. The issue has now been fixed, so both the with and without slash versions of API endpoints work as before. Apologies for the inconvenience. Regards, Chris On 30/04/2020 10:25, Robert Kisteleki wrote:
On 2020-04-30 08:50, Benjamin Collet wrote:
Hi,
On Thu, Apr 30, 2020 at 08:25:26AM +0200, Stephane Bortzmeyer wrote:
The redirect is to a slightly different URL. OK, thanks, I did not notice the detail. But it worked before (I use it in a monitoring script), and the behavior changed somewhere around 29 april, 13:20 UTC. Same behaviour here. The fix is easy enough but it would be nice to be warned when API endpoints change, or did I miss something? Hello,
We deployed some changes around the date Stephane mentioned. This was not intended to affect the URL behaviour, and we're investigating why this is happening. We'll get back to you soon.
In the meantime: api/xxx/?parameters (ie. with a slash at the end of the URL before the potential parameters) works as intended so you can use this form, at least for now.
Regards, Robert
participants (5)
-
Benjamin Collet -
Chris Amin -
Philip Homburg -
Robert Kisteleki -
Stephane Bortzmeyer