From: Kenji Arisawa <arisawa@ar.aichi-u.ac.jp>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] utf-8 text files from httpd
Date: Mon, 19 Oct 2009 11:16:28 +0900 [thread overview]
Message-ID: <F273F7AF-0DC7-420D-AF92-692BED92CDFB@ar.aichi-u.ac.jp> (raw)
In-Reply-To: <fe41879c0910181734l6363baebsa896bda992d690@mail.gmail.com>
according to rfc2616, default charset in sending text file is ascii:
The "charset" parameter is used with some media types to define the
character set (section 3.4) of the data. When no explicit charset
parameter is provided by the sender, media subtypes of the "text"
type are defined to have a default charset value of "ISO-8859-1"
when
received via HTTP. Data in character sets other than "ISO-8859-1" or
its subsets MUST be labeled with an appropriate charset value. See
section 3.4.1 for compatibility problems.
httpd need explicitly charset=utf-8 in http header in sending utf-8
text.
Kenji Arisawa
On 2009/10/19, at 9:34, Akshat Kumar wrote:
> I'm trying to put up a plain text file containing UTF-8
> characters from httpd, but when viewing it from any
> browser, it comes off as an ASCII file that needs to
> be downloaded (so, those characters are garbled).
> Is this due to some behaviour of httpd?
>
> ak
>
next prev parent reply other threads:[~2009-10-19 2:16 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-19 0:34 Akshat Kumar
2009-10-19 1:39 ` andrey mirtchovski
2009-10-19 2:16 ` Kenji Arisawa [this message]
2009-10-19 3:35 ` Kenji Arisawa
[not found] <<fe41879c0910181734l6363baebsa896bda992d690@mail.gmail.com>
2009-10-19 1:37 ` erik quanstrom
2009-10-19 10:00 ` Akshat Kumar
2009-10-19 12:45 ` Kenji Arisawa
[not found] <<A6127A93-8E78-4E11-9284-56A16D2A2093@ar.aichi-u.ac.jp>
2009-10-19 4:46 ` erik quanstrom
2009-10-19 9:05 Eris Discordia
[not found] <<fe41879c0910190300l51480646pf9630e90c6f30207@mail.gmail.com>
2009-10-19 13:14 ` erik quanstrom
2009-10-19 13:49 ` roger peppe
[not found] <<df49a7370910190649k3179f0b1r4c877d5ca72af232@mail.gmail.com>
2009-10-19 13:55 ` erik quanstrom
2009-10-19 14:32 ` roger peppe
2009-10-19 17:36 ` lucio
[not found] <<df49a7370910190732i526a15b6o6d2822cd2d14bff0@mail.gmail.com>
2009-10-19 14:50 ` erik quanstrom
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=F273F7AF-0DC7-420D-AF92-692BED92CDFB@ar.aichi-u.ac.jp \
--to=arisawa@ar.aichi-u.ac.jp \
--cc=9fans@9fans.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).