[atlas] 400 Bad Request - tnx + another Q
- Previous message (by thread): [atlas] 400 Bad Request
- Next message (by thread): [atlas] Ennit Server (DE) has joined RIPE Atlas anchors
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Wilfried Woeber
Woeber at CC.UniVie.ac.at
Sat Mar 22 15:26:01 CET 2014
Thanks Robert, now works like a charm :-) Just out of curiosity - is the probe ID a link only during those periods when it is "down"? Asking because I have another one (ID = 12711) which is "up" and the Id isn't clickable. Low prio, just trying to understand what the algorithm is. Cheer, Wilfried. Robert Kisteleki wrote: > Wilfried, > > Thank you for the report, this is now fixed. > > Regards, > Robert > > > On 2014.03.21. 22:31, Wilfried Woeber wrote: > >>Hi folks, >> >>I had a look at the list of my ambassador probes and noticed that one of >>them is currently listed as being off-line (ID 12734) >> >>The probe ID is rendered as a link, with this URL: >> >>https://atlas.ripe.net/ambassadors/probes/%7B%%20url%20'probe-detail'%20pk=record.prb_id%20%7D%7D >> >>which comes back with >>" >>Bad Request >> >>Your browser sent a request that this server could not understand. >>" >> >>Just fyi, no harm done :-) >>Cheers, >>Wilfried >> >> > >
- Previous message (by thread): [atlas] 400 Bad Request
- Next message (by thread): [atlas] Ennit Server (DE) has joined RIPE Atlas anchors
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]