[Plugin: WP Super Cache] If permalink has 2bytes characters, cache isn’t made.

First access (the permalink has 2bytes characters)
↓
wp super cache make cache file
/wp-content/cache/supercache/example.com/2009/08/22/%e3%83%86%e3%82%b9%e3%83%88/index.html
↓
Second time access
↓
Cache file exists but .htaccess doesn’t rewrite url and wp super cache make cache file again

mod_rewrite has problems with unicode and urlencoded urls. The bug has been around for ages.

Because two urls refer to the same resource, the workaround is lots and lots of symlinks. I doubt donncha will decide to go this route.

Half-on is the best you can do.

I could urldecode the request uri before creating the cached file and directories but I don’t know if that will have security implications.

Some filesystems won’t allow certain characters to be in filenames for example.

What patch and configs did you use to get the japanese characters to work in the url? I’ve added the support in the .htaccess* in the webbserver. I also added the wp-multibyte-patch, but can’t get the kanjis, hiraganas and katakanas to show. Just a strange combinations of numbers, letters and %-symbols are being shown, like in yur example.

*

# BEGIN WordPress
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]
</IfModule>
# END WordPress

satovic – you’re better off using the plugin in half-on mode.