New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
bug: investigate possible regression with fallback path #31
Comments
Lines 281 to 287 in b0dc025
This may be the culprit, we should checking for the fallback path when we load the config, and also before we send a plain 404 |
Also here: Lines 271 to 276 in b0dc025
We are checking for rewrites and redirects but again, nothing about the fallback (which I am guessing has to do with the logic in the function to get a valid path |
I take it back, we seem to be doing the necessary checks at first glance but I will have a look again properly tomorrow Lines 176 to 183 in b0dc025
|
Actually, this seems like it's happening specifically for |
Right! This is because the projects directory exists after building but it only contains images, so we are clearly not checking for the absence of that index.html and falling back somewhere. This is the file tree after building: projects/ |
This fixes #31 where it would render an empty 404 if the directory exists but has no index file in it.
This fixes #31 where it would render an empty 404 if the directory exists but has no index file in it.
Latest deployment of my website does not seem to be falling back to 404.html as expected
The text was updated successfully, but these errors were encountered: