tangled.org
this is recognized by safari. the only size this image is served at is 48x48. the dolly silhouette is used. cache/etag headers are identical to the svg output.
Signed-off-by: oppiliappan me@oppi.li
Monorepo for Tangled
tangled.org
appview: serve ico favicons on /favicon.ico #938
closed
opened by
oppi.li
targeting
master
from
op/lrpyxormllvp
expand 1 commit
hide 1 commit
appview: serve ico favicons on /favicon.ico
this is recognized by safari. the only size this image is served at is
48x48. the dolly silhouette is used. cache/etag headers are identical to
the svg output.
Signed-off-by: oppiliappan <me@oppi.li>
right the same code can be employed to generate it at build time. the main benefit is that we can have a single template to generate all assets without things going stale.
unable to resubmit this for some reason, will investigate shortly!
closed without merging
If it is static, I think we should generate it on build time. From
appview-static-filesor at least on appview initialization. While cache/etag can reduce recall, that is still inefficient endpoint.