aboutsummaryrefslogtreecommitdiff
path: root/doc/bugs/404_plugin_should_handle_403.mdwn
diff options
context:
space:
mode:
Diffstat (limited to 'doc/bugs/404_plugin_should_handle_403.mdwn')
-rw-r--r--doc/bugs/404_plugin_should_handle_403.mdwn10
1 files changed, 9 insertions, 1 deletions
diff --git a/doc/bugs/404_plugin_should_handle_403.mdwn b/doc/bugs/404_plugin_should_handle_403.mdwn
index 71aed632e..50288e525 100644
--- a/doc/bugs/404_plugin_should_handle_403.mdwn
+++ b/doc/bugs/404_plugin_should_handle_403.mdwn
@@ -1,7 +1,15 @@
-Apache will return 403 (Forbidden) instead of 404 (Not Found) if the `Indexes` option is turned off. This is because with `Indexes` turned on, it considers it something it *might* be able to serve in the future. With `Indexes` off, it will never serve that page in the future (unless `Indexes` is turned back on).
+Apache will return 403 (Forbidden) instead of 404 (Not Found) if the
+`Indexes` option is turned off. This is because with `Indexes` turned on,
+it considers it something it *might* be able to serve in the future. With
+`Indexes` off, it will never serve that page in the future (unless
+`Indexes` is turned back on).
The [[404 plugin|plugins/404]] code only checks for 404, not 403. It should check for both.
+> There are plenty of reasons a web server might 403. In most of those
+> cases, trying to create a page where the forbidden content is is not the
+> right thing for ikiwiki to do. --[[Joey]]
+
See Also:
* [StackOverflow: 404-vs-403](http://stackoverflow.com/questions/5075300/404-vs-403-when-directory-index-is-missing)