I also notice that the PNG gets an asset/favicon.png route as well as a /favicon.png route, in API Gateway, even though it definitely is not located at asset/favicon.png. This may somehow be an artifact of my build pipeline, I'm not sure 🤔
actually, it seems like the browser gets a 200 but the image is broken?
...clearly not broken there? But broken in the browser... there may be something weird about the way its content type is described
12/13/2020, 11:00 PM
Hm, I am having same problems with favicon on site. Have you checked between different browsers?
12/14/2020, 8:27 PM
I just got a moment to test it -- it doesn't work in Edge nor Firefox; and in Firefox it sees the response body as an image/png with 0x0 dimensions, and the page is displayed as "The image "..." cannot be displayed because it contains errors"
Have you gotten working favicons served through kotless previously? Maybe I could follow a certain model