Yep, looks fine ... although the
mod_rewrite is not functioning correctly ... and this reflects on your website also ...
The strange thing is, if you access the image with the rewrite, it gives an error message ...
http://voyagedanslinstant.com/diag/image.jpg
The requested URL /kunden/homepages/36/d278437577/htdocs/voyagedanslinstant.com/public/kunden/homepages/36/d278437577/htdocs/voyagedanslinstant.com/diag/image/image.jpg was not found on this server.
Hmm look at that path ... It is somehow doubling up on itself, so obviously the path becomes wrong. The end part is correct:
voyagedanslinstant.com/diag/image/image.jpg, because the image is in fact there
voyagedanslinstant.com/diag/image/image.jpg, but your server is creating wrong server path up front. It seems rewrite_mod is configured incorrectly, or something else on the server.
If you have FTP, I might look around and try some solutions ... If not, it is difficult for me to suggest any solutions except for contacting your server host and forwarding this message.
The mod_rewrite test is very basic. Inside the diag folder, there is .htaccess with:
RewriteEngine on
# Rewrite any file calls to the image directory
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteCond %{REQUEST_URI} !image/
RewriteRule ^(.+)$ image/$1 [L]
... which simply takes a file request, for example
diag/image.jpg, and rewrites to the location where file actually is [urlhttp://voyagedanslinstant.com/diag/image/image.jpg]diag/image/image.jpg[/url]. Your host must have something to say about this ...
