Making 404 status response optional when non-existent url is requested - Github Pages #63876
Unanswered
PixelatedLagg
asked this question in
Pages
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Select Topic Area
Product Feedback
Body
This seems like a really small thing that doesn't affect a lot of people, but it is quite the opposite. Here's the conflict: me and all the other freeloaders want to host SPA websites on Github Pages. Using some janky hacks, it is all possible - except that dastardly 404 response. That little bit of code on Github servers single-handedly stops any attempts at using OpenGraph or storing any meta tags that crawlers would like to access.
On behalf of me and all the other hooligans, I would like to ask that Github makes the 404 status optional in the 404.html response. It doesn't even have to be some secret setting stored in a private database - we would all be completely fine with having another file in the root directory, just like with the domain name. On top of that, having a configuration file in the directory would open the door to any other requested Github Pages hosting settings.
Beta Was this translation helpful? Give feedback.
All reactions