The thing is… this is a direct file access. It should not even be looking at at the templates and snippets.
Its bascially a vanilla .htacess file. All ive really done is added rules for Gzip to the standard rules that come with Kirby. The issue persists even with the vanilla Kirby .htaccess.
I should be able to directly hit an image file, surely??
What do you mean by “a direct hit to an image”? Where? What code? If the snippet wasn’t called and just lived quietly in its folder, it wouldn’t throw an error.
I cannot directly access any of those files in a browser, not even images, because it throws a whoops page.
they are all in /assets/images/favicon/ so i thnk something in Kirbies .htaccess files or somewhere else is restricting access to only certain folders under the assets folder.
But it seems to be treating it like a page and trying to process a template for the file, which is breaking it.
I can’t reproduce this issue; I have several sites on localhost and remote with such a favicons folder and no problem at all. Could you please post the complete error message and your .htaccess file? Do you get the same issue with a fresh starter kit (and those favicons) on that server?
Hmmm thats odd. Now i have rebooted the server and come back to work this morning, it seems to be working. Very strange. However, i do still get a whoops page if i hit a file that doesn’t exist. Shouldn’t this use the sites error page instead? The one in my templates?