On Fri, Nov 12, 2004 at 12:56:30PM +0100, Laurent Wacrenier wrote: > >Also useful > > is a tcpdump of the HTTP session between the client and browser when > > fetching that page: try something like > > tcpdump -i eth0 -n -s1500 -X tcp port 80 >tcpdump.out > > on the server. > > tcpdump is unusable on a server with a lot of people connecting.
# tcpdump -i eth0 -n -s1500 -X tcp port 80 and host x.x.x.x where x.x.x.x is the IP address of the client host. Or just test from localhost and use -i lo(0). > Just drop a file with this in your Maildir/cur folder > > ------- > From [EMAIL PROTECTED] Fri Nov 12 11:58:01 2004 > Return-Path: <[EMAIL PROTECTED]> > Date: Fri, 12 Nov 2004 11:58:00 +0100 > From: Laurent Wacrenier <[EMAIL PROTECTED]> > To: [EMAIL PROTECTED] > Subject: test > Mime-Version: 1.0 > Content-Type: text/html; charset=iso-8859-15 > Content-Disposition: inline > Content-Transfer-Encoding: quoted-printable > > euro: =A4 > > ------- OK. In mozilla for me it renders as "euro: " then a diamond containing a question mark. I ran a tcpdump. It shows Content-Type: text/html; charset=utf-8 and <?xml version="1.0" encoding="utf-8"> Then the hex output around the bad area is: 0x0350 3025 223e 3c74 723e 3c74 643e 0a65 7572 0%"><tr><td>.eur 0x0360 6f3a 20a4 0a0a 3c2f 7464 3e3c 2f74 723e o:....</td></tr> OK, well that demonstrates the problem; the byte a4 has been output directly instead of being converted to UTF-8. Thank you; that is a sufficiently full demonstration of the problem that someone who knows the code should be able to fix it quickly. That person isn't me, but perhaps Sam will pick this up. Regards, Brian.
