t/git-cgi.t: fix race condition

[git.ikiwiki.info.git] / doc / bugs / 404_plugin_should_handle_403.mdwn

diff --git a/doc/bugs/404_plugin_should_handle_403.mdwn b/doc/bugs/404_plugin_should_handle_403.mdwn
index 71aed632ec81dea89b4d0557e353bca6477da4bf..50288e525b6ba362504215644880ffb38dbd9692 100644 (file)
--- 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.
 
 
 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)
 See Also:
 
  * [StackOverflow: 404-vs-403](http://stackoverflow.com/questions/5075300/404-vs-403-when-directory-index-is-missing)