Dear Stephane, Thank you for pointing this out, it has been fixed: the anchors respond with a proper 404 now. Regards, Robert, reporting for the people who fixed it On Thu, Apr 4, 2024 at 6:48 PM Stephane Bortzmeyer <bortzmeyer@nic.fr> wrote:
It seems the anchors, when receiving a HTTP request for a non-existing path, instead of a 404, send a broken response:
% curl -v http://fr-par-as2486.anchors.atlas.ripe.net/nonono * Trying 2001:67c:217c:4::2:80... * Connected to fr-par-as2486.anchors.atlas.ripe.net (2001:67c:217c:4::2) port 80 (#0)
GET /nonono HTTP/1.1 Host: fr-par-as2486.anchors.atlas.ripe.net User-Agent: curl/7.81.0 Accept: */*
* Empty reply from server * Closing connection 0 curl: (52) Empty reply from server
-- ripe-atlas mailing list ripe-atlas@ripe.net https://lists.ripe.net/mailman/listinfo/ripe-atlas