- From: Martin Thomson <martin.thomson@gmail.com>
- Date: Fri, 20 Feb 2015 08:04:30 +1100
- To: Brad Hill <hillbrad@gmail.com>
- Cc: Anne van Kesteren <annevk@annevk.nl>, WebAppSec WG <public-webappsec@w3.org>, WebApps WG <public-webapps@w3.org>, Monsur Hossain <monsur@gmail.com>, Jonas Sicking <jonas@sicking.cc>, Dale Harvey <dale@arandomurl.com>
On 18 February 2015 at 06:31, Brad Hill <hillbrad@gmail.com> wrote: > Some of the things that argue against /.well-known are: > > 1) Added latency of fetching the resource. It's not available everywhere yet, but you could push it, based on the below. > 2) Clients hammering servers for non-existent /.well-known resources (the > favicon issue) You could avoid that by Link:-ing to the /.well-known and only hitting it if the link appears.
Received on Thursday, 19 February 2015 21:05:00 UTC