[atlas] Error: Only anchors may be targeted.
- Previous message (by thread): [atlas] Error: Only anchors may be targeted.
- Next message (by thread): [atlas] Actual measurement interval much larger than planned
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Thomas Bartelmess
thomas at bartelmess.io
Fri Oct 21 15:05:46 CEST 2016
My wish list would look like: - Limits on how many tests are run against a specific target (globally) - Robots.txt/SRV Record to increase the limit - Ability to see if ISP injected Headers (Supercookies) - Ability if the server changes anything about the website (Ads etc). - Verify TLS certificates - Thomas > On Oct 21, 2016, at 3:29 , Marat Khalili <mkh at rqc.ru> wrote: > > I don't know how hard it'd be to implement, but it'd be natural to use robots.txt for this. Something like: > >> User-agent: RIPE-ATLAS >> Allow: /test-me-here/ > It would need to be checked both on control centers (to make sure probing is allowed at all) and on probes (to react on changes quickly). > > > -- > > With Best Regards, > Marat Khalili > > On 21/10/16 07:49, Joseph B wrote: >>> Indeed, it would be really useful to be able to measure http/https sites >>> from atlas probes. >> As a network operator, even if those measurements were only allowed >> inside our own (or downstream) AS's that would be vary useful. >> >> Cheers, >> >> Joseph >> > > -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 4564 bytes Desc: not available URL: <https://lists.ripe.net/ripe/mail/archives/ripe-atlas/attachments/20161021/0873048a/attachment.p7s>
- Previous message (by thread): [atlas] Error: Only anchors may be targeted.
- Next message (by thread): [atlas] Actual measurement interval much larger than planned
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]