If you save the .htaccess file using ISO-8859-1 or Windows 1252
encodings, it works fine. But if you use utf-8 recommended and
universal encoding, Apache triggers an "Internal Server Error". I have
tried several hours creating some rules, and when I found out nothing
worked, all of the sudden I saw Apache did not accept utf-8. Most
operating systems and applications are migrating to utf-8 to support
international languages, so it would be a good thing to work properly
with utf-8.

On 2007-02-02, Charles <landemaine@gmail.com> wrote:
> If you save the .htaccess file using ISO-8859-1 or Windows 1252
> encodings, it works fine. But if you use utf-8 recommended and

Don't post this here, maybe file a bug report in the bugzilla db
of apache.

Davide

--
Another name for a Windows tutorial is "crash course".

Il 02/02/2007 19:19, Charles dixit:
> If you save the .htaccess file using ISO-8859-1 or Windows 1252
> encodings, it works fine. But if you use utf-8 recommended and
> universal encoding, Apache triggers an "Internal Server Error".

My 1.3.37 don't show this problem, even inserting multibyte characters
just like in these two snippets (saved as UTF-8):

Order Deny,Allow
Deny from liberté.egalité.fraternité.com
Allow from 10.1.1.2

Order Deny,Allow
Deny from (جريدة الأهرام - الصÙ�ØØ© الأو(¹
Allow from 10.1.1.2

I guess there could be just an "offending" character, somewhere: maybe
you can try to insulate the problem by splitting the .htaccess in
smaller pieces.

I got an Internal Server Error using // instead # to comment away a
line, if this could be useful to someone.

Cyrus (the /perplexed/ virus)


(¹) Got it googling for "Al Ahram", the Egyptian newspaper.

--
I love to be mailed just by smart people:
perl -we 'print "\12\142\145\162\156\141\155\141\100\151".
"\164\167\145\142\56\151\164\12\12";'
Spammers scratch here with a diamond to find my address:
|||||||||||||||||||||||||||||||||||||||||||||||

On 2 Feb, 19:16, cyrusthevirus <r...@127.0.0.1> wrote:
> Il 02/02/2007 19:19, Charles dixit:
>
> > If you save the .htaccess file using ISO-8859-1 or Windows 1252
> > encodings, it works fine. But if you use utf-8 recommended and
> > universal encoding, Apache triggers an "Internal Server Error".
>
> My 1.3.37 don't show this problem, even inserting multibyte characters
> just like in these two snippets (saved as UTF-8):
>
> Order Deny,Allow
> Deny from liberté.egalité.fraternité.com
> Allow from 10.1.1.2
>
> Order Deny,Allow
> Deny from (جريدة الأهرام - الصÙ�ØØ© الأو (¹
> Allow from 10.1.1.2
>
> I guess there could be just an "offending" character, somewhere: maybe
> you can try to insulate the problem by splitting the .htaccess in
> smaller pieces.
>
> I got an Internal Server Error using // instead # to comment away a
> line, if this could be useful to someone.
>
> Cyrus (the /perplexed/ virus)
>
> (¹) Got it googling for "Al Ahram", the Egyptian newspaper.
>
> --
> I love to be mailed just by smart people:
> perl -we 'print "\12\142\145\162\156\141\155\141\100\151".
> "\164\167\145\142\56\151\164\12\12";'
> Spammers scratch here with a diamond to find my address:
> |||||||||||||||||||||||||||||||||||||||||||||||

are you sure its not just the /way/ you are saving the utf-8 doc.
The so called Byte-Order-Mark (BOM) often causes these kinds of
issues, depending on the editor you were using it might not have shown
up, but if you goto the end of the doc and delete all lines but the
first, then starting at the end of the line hold the delete key down
until it gets to the start of the doc and save, you will see the file
is of length 1byte, whereas pressing alt+A and then delete and save
will result in 0bytes.
Its this BOM that trips stuff up, whereas apache should be able to
cope with utf-8.