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/mat-wg@ripe.net/
[mat-wg] [atlas] Proposal for public HTTP measurements
- Previous message (by thread): [mat-wg] [atlas] Proposal for public HTTP measurements
- Next message (by thread): [mat-wg] [atlas] Proposal for public HTTP measurements
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Robert Kisteleki
robert at ripe.net
Wed Jan 7 09:13:53 CET 2015
Hi, On 2015-01-05 14:35, Brian Trammell wrote: > Since the target will be an anchor which has known expected content, will > these measurements include some indication of whether application-layer > rewriting was detected? The primary purpose is to measure and to collect and provide this data. We can surely implement such checks and related visualisations in the UI and perhaps, if there's support for it, in the form of status checks (see https://atlas.ripe.net/docs/status-checks/). However, first I'd like to see consensus on what data we should collect, if any :) Regards, Robert
- Previous message (by thread): [mat-wg] [atlas] Proposal for public HTTP measurements
- Next message (by thread): [mat-wg] [atlas] Proposal for public HTTP measurements
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ mat-wg Archives ]