On 18 February 2015 at 06:31, Brad Hill <hillb...@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.

Reply via email to