Skip to content

Why does a GitHub Pages site without an index.html file returns 403 instead of 404? #22182

Discussion options

You must be logged in to vote

This is a great question! It’s a 403 because the site and URL exist, but 403 errors are defined as: “This error is typically caused by faulty file permissions. The application pool user does not have the correct permissions to access or modify the resource in question.”

So it essentially knows there’s a site there, and is looking for an index.HTML file, but it can’t find it hence it thinks it doesn’t have permission.

Replies: 1 comment

Comment options

You must be logged in to vote
0 replies
Answer selected
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
2 participants