This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/ripe-atlas@ripe.net/
[atlas] HTTP UDM?
- Previous message (by thread): [atlas] HTTP UDM?
- Next message (by thread): [atlas] HTTP UDM?
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Miles McCredie
atlas at net-principles.com
Fri Aug 3 17:36:12 CEST 2012
On 8/3/12 02:37 , Daniel Karrenberg wrote: > it will be very basic and definitely not be there to compete with > widely available "web site testing". > It will likely be very restrictive on the amount of data it fetches and the number of probes. RIPE Atlas is designed as a network level measurement tool and not an application tester. > > We are also somewhat concerned about consequences for our probe hosts. Consider what can happen if an atlas user causes your probe to access content that is considered inappropriate or even illegal where you live and run your probe. Understood. Some thoughts: - Restrict the UDM to retrieving /robots.txt. (Generally innocuous/legal content and not too large?) - Limit the UDM to retrieving 4500 bytes or so of data and then sending a RST. (Enough data to confirm max MTU frames can be received but not enough to contain inappropriate or illegal content?) - Send a RST after receiving a SYN-ACK response. (Would be useful to allow port configuration in this case to allow tests for filtering.) Thanks -Miles
- Previous message (by thread): [atlas] HTTP UDM?
- Next message (by thread): [atlas] HTTP UDM?
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]