HTTP Request

«Known» request paths

/favicon.ico

See also <link rel="icon" ‥>, for example

<link rel="icon" type="image/png" sizes="32x32" href="/apps/core/docroot/images/design/sgch/favicon/favicon-32x32.png">
<link rel="icon" type="image/png" sizes="16x16" href="/apps/core/docroot/images/design/sgch/favicon/favicon-16x16.png">

/robots.txt

See here.

/.well-known

/.well-known/‥ URLs allow a web server to provide information about itself.

The Well-Known URIs list is maintained at https://www.iana.org/assignments/well-known-uris/well-known-uris.xhtml.

Some (imho) interesting suffixes include:

`acme-challenge`
`appspecific`	For example: `/.well-known/appspecific/com.chrome.devtools.json`.
`core`	Constrainted RESTful Environments (CoRE) Link Format
`csvm`	CSV metadata (see also CSV on the Web).
`nostr.json`	See NIP-05
`opencode`
`security.txt`	Information to find the responsible security contact in case of a security issue, see for example https://www.admin.ch/.well-known/security.txt
`traffic-advice`	Compare with Google's AMP (Accelerated Mobile Pages).

See also RFC 8615 (Well-Known Uniform Resource Identifiers (URIs))

TODO: I've also seen https://register.ld.admin.ch/.well-known/dataset/foj-zefix (of which I am not sure where this is documented).

/wp-admin/install.php

/wp-admin/install.php seems to be an URI that automated bots like to access.