Hi! I'm serving a static directory from the root (...

# kotless

[Sebastian Kazenbroot-Guppy]

Hi! I'm serving a static directory from the root (mywebsite.com/thisasset.extension) with 4 files in it: a JavaScript file, a CSS file, an HTML file, and a favicon called "favicon.png". The first three files load just fine when CURL'd/navigated to in a browser, but the favicon returns a 403. Using the API Gateway dashboard "Test" view, the favicon can be retrieved just fine. Is there something that could be different about this PNG?

[Sebastian Kazenbroot-Guppy]

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 🤔

[Sebastian Kazenbroot-Guppy]

actually, it seems like the browser gets a 200 but the image is broken?

https://memo.sebastiankazenbrootguppy.com/favicon.png▾

[Sebastian Kazenbroot-Guppy]

...clearly not broken there? But broken in the browser... there may be something weird about the way its content type is described

[TanVD]

Hm, I am having same problems with favicon on site. Have you checked between different browsers?

[Sebastian Kazenbroot-Guppy]

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"

[Sebastian Kazenbroot-Guppy]

Have you gotten working favicons served through kotless previously? Maybe I could follow a certain model

[TanVD]

Yep, it worked few months before :) I’ll check)