aboutsummaryrefslogtreecommitdiff
path: root/doc/bugs
diff options
context:
space:
mode:
authorJoey Hess <joey@gnu.kitenet.net>2009-07-12 21:32:24 -0400
committerJoey Hess <joey@gnu.kitenet.net>2009-07-12 21:32:24 -0400
commita41a12ab9a7206d324ad198e287a37fc17172f18 (patch)
tree514df3292c4901437bb8f8d7db82d0e4b98e8ae9 /doc/bugs
parent95590417cf9b72cd943c2544bc2e80872da840e3 (diff)
downloadikiwiki-a41a12ab9a7206d324ad198e287a37fc17172f18.tar
ikiwiki-a41a12ab9a7206d324ad198e287a37fc17172f18.tar.gz
response
Diffstat (limited to 'doc/bugs')
-rw-r--r--doc/bugs/CGI_problem_with_some_webservers.mdwn12
1 files changed, 12 insertions, 0 deletions
diff --git a/doc/bugs/CGI_problem_with_some_webservers.mdwn b/doc/bugs/CGI_problem_with_some_webservers.mdwn
index 7cfc53741..3f80bbbd6 100644
--- a/doc/bugs/CGI_problem_with_some_webservers.mdwn
+++ b/doc/bugs/CGI_problem_with_some_webservers.mdwn
@@ -68,6 +68,8 @@ Why do they appear two times with conflicting values in the very same hashes?
Marking [[done]] since it's not really an ikiwiki bug. --[[Joey]]
+----
+
I'm getting some odd behaviour with boa. When I edit a page and click "Save
Page", the URL I get taken to produces a 403 - Forbidden error until I recompile
the wiki. For example, after editing the root page of the wiki it brings me back to
@@ -89,5 +91,15 @@ permissions. Boa was then rightly refusing to serve the page. Adding the
`umask 022` config option to `ikiwiki.setup` fixed everything, and all
appears to be working fine now. --Paul.
+> Since others seem to have gotten ikiwiki working with boa,
+> I'm guessing that this is not a generic problem with boa, but that
+> your boa was started from a shell that had an unusual umask and inherited
+> that. --[[Joey]]
+
(I'm new to wiki etiquette - would it be more polite to leave these details on the
wiki, or to remove them and only leave a short summary? Thanks. --Paul)
+
+> Well, I just try to keep things understandable and clear, whether than
+> means deleting bad old data or not. That said, this page is a bug report,
+> that was already closed. It's generally better to open a new bug report
+> rather than edit an old closed one. --[[Joey]]