On 3/3/06, John N. Brahy <[EMAIL PROTECTED]> wrote:
>
> > Well, all bets are off with openbsd, since their version of apache is
> > forked (contains non-standard patches).
> >
> > But in general, AddDefaultCharset has an effect only if there are no
> > AddCharset directives applying to the files.  And your AddCharset
> > directive above probably does nothing unless all your files have a
> > .utf8 filename extension.
> >
> > But the first question is really, how do you know you are still
> > getting iso-8859-1?  Have you checked the http response headers?
> >
> > Joshua.
>
> The reason that I know it's not utf-8 is by a few reasons,
> 1) wget -S says it's Content-Type: text/html; charset=ISO-8859-1
> 2) when I try the HTML validator on w3c.org it tells me that it's
> ISO-8859-1
> 3) Internet Explorer and Firefox both have ISO-8859-1 selected
> 4) Firefox's Page Info shows it as ISO-8859-1
>
> Is there a way to remove all other content types and only output utf-8
> or would I have to hack the source for that to work? If so could you
> point me to the place in the source to modify?
>
> I'm using mod_perl for almost everything but the few pages that I'm not
> have a .ad2 extension. I added "AddCharset UTF-8 .ad2" but that doesn't
> see to change anything.

Are these static files, or are they generated by some dynamic handler?
 Can you give us an internet-accessible example URL?  Are you sure
that your AddCharset and AddDefaultCharset directives are in the right
place in the right config files?

Joshua.

---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: [EMAIL PROTECTED]
   "   from the digest: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to