Re: HTTP-Header charset different to charset encoding
Hi, I'm a little rusty on this, but if I remember correctly most browsers will first try to identify the content using the HTTP header and use the HTTP body or even the file extension as second options. Some browsers gave preference to file extension before body. One way to find out what standard browser behavior 'should' be, is to test against Internet Explorer and then do exactly the opposite ;-) Cheers, Jacobus On Fri, Mar 12, 2010 at 3:44 PM, Bartolomeo Nicolotti <bnicolotti@xxxxxxxxx> wrote: > Hello, > > only a quick question. I've to handle xml in the body of an HTTP response. > The problem is that http header can specify an encoding different from the processing instruction, like here: > > HTTP-Header: > > Content-Type: application/xhtml+xml; charset=UTF-8 > > > 1: <?xml version="1.0" encoding="ISO-8859-1"?> > 2: <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" > 3: "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> > 4: > 5: <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="de" lang="de"> > 6: <head> > 7: <title>HTTP != XML</title> > 8: </head> > 9: <body>dv|DV\_</body> > 10: </html> > > Which encoding has precedence? The http header or the processing instruction? > > Many thanks > > Best regards > > Bartolomeo Nicolotti > > -- Good ideas will be done
PURCHASE STYLUS STUDIO ONLINE TODAY!
Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced!
Download The World's Best XML IDE!
Accelerate XML development with our award-winning XML IDE - Download a free trial today!
Subscribe in XML format