aboutsummaryrefslogtreecommitdiff
path: root/doc/bugs/Pages_with_non-ascii_characters_like_öäå_in_name_not_found_directly_after_...
diff options
context:
space:
mode:
authorJoey Hess <joey@kitenet.net>2011-01-25 14:39:20 -0400
committerJoey Hess <joey@kitenet.net>2011-01-25 14:39:20 -0400
commite2a501454637ca922f5d567f835039b38a8351c8 (patch)
treeddc01987fbab12155c9b93c42d7128f20fa45160 /doc/bugs/Pages_with_non-ascii_characters_like_öäå_in_name_not_found_directly_after_commit.mdwn
parentf2c298a20fcf080b0c9f79828e2db608e2e27e8f (diff)
downloadikiwiki-e2a501454637ca922f5d567f835039b38a8351c8.tar
ikiwiki-e2a501454637ca922f5d567f835039b38a8351c8.tar.gz
response
Diffstat (limited to 'doc/bugs/Pages_with_non-ascii_characters_like_öäå_in_name_not_found_directly_after_commit.mdwn')
-rw-r--r--doc/bugs/Pages_with_non-ascii_characters_like_öäå_in_name_not_found_directly_after_commit.mdwn13
1 files changed, 12 insertions, 1 deletions
diff --git a/doc/bugs/Pages_with_non-ascii_characters_like_öäå_in_name_not_found_directly_after_commit.mdwn b/doc/bugs/Pages_with_non-ascii_characters_like_öäå_in_name_not_found_directly_after_commit.mdwn
index e7cb43bee..a08ec6fd0 100644
--- a/doc/bugs/Pages_with_non-ascii_characters_like_öäå_in_name_not_found_directly_after_commit.mdwn
+++ b/doc/bugs/Pages_with_non-ascii_characters_like_öäå_in_name_not_found_directly_after_commit.mdwn
@@ -7,4 +7,15 @@ Happens also after editing the page. Here's an example:
* page name displayed in 404: http://mcfrisk.kapsi.fi/skiing/posts/Iso-Sy%F6te%20Freeride%202011%20Teaser.html?updated
* page name in the blog feed: http://mcfrisk.kapsi.fi/skiing/posts/Iso-Sy%C3%B6te%20Freeride%202011%20Teaser.html
-Difference is in the word Iso-Syöte. Pehaps also the browsers is part of the game, I use Iceweasel from Debian unstable with default settings.
+Difference is in the word Iso-Syöte. Pehaps also the browsers is part of
+the game, I use Iceweasel from Debian unstable with default settings.
+
+> I remember seeing this problem twice before, and both times it was caused
+> by a bug in the *web server* configuration. I think at least one case it was
+> due to an apache rewrite rule that did a redirect and mangled the correct
+> encoding.
+>
+> I recommend you check there. If you cannot find the problem with your web
+> server, I recommend you get a http protocol dump while saving the page,
+> and post it here for analysis. You could use tcpdump, or one of the
+> browser plugins that allows examining the http protocol. --[[Joey]]