views:

4468

answers:

4

I've got a php script. Most of the time the script returns html, which is working fine, but on one occasion (parameter ?Format=XML) the script returns XML instead of HTML.

Is there any way to change the returned mime type of the php output on the fly from text/html to text/xml or application/xml?

+8  A: 
header('Content-type: text/xml');

More information available at the PHP documentation: http://au.php.net/manual/en/function.header.php

nickf
+2  A: 

Set the Content-Type header:

header('Content-Type: text/xml');

Though you should probably use "application/xml" instead.

John Millikin
You got me - what is the difference between text/xml and application/xml, though?
Sam
Interactions between text/* content types HTTP regarding encoding, mainly: see http://annevankesteren.nl/2005/03/text-xml
John Millikin
Caching proxies are allowed to edit `text/*` to change the character encoding. Since XML also declares its character encoding inside the document itself, you really don't want that to happen, as you might get a mismatch. So use `application/xml` instead, and caching proxies will see the content as binary data and leave it undisturbed.
TRiG
+1  A: 

You should send a Content-Type header before you send any output header('Content-Type: text/xml');

andy.gurin
+1  A: 

I will answer to the update, since the previous answers are good.
I have read that Internet Explorer is well known for ignoring Mime type headers (most of the time?) to rely on content of the file (which can cause problems in some cases).

Mmm, I did a simple test:

<?php
header('Content-Type: text/xml');
echo '<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<root><foo a="b">Tada</foo></root>';
?>

Internet Explorer 6 displays it correctly as XML. Even if I remove the xml declaration.
You should indicate which version is problematic.

Actually, as I wrote above, with IE (6 at least), you don't even need a content-type, it recognize XML data and display it as a tree. Is your XML correct?

[Update] Tried with IE7 as well, adding ?format=xml too, still displaying XML correctly. If I send malformed XML, IE displays an error. Tested on WinXP Pro SP2+

PhiLho
Sorry, my mistake, the example code I copied did sent the XML through htmlentities for output, and I didn't notice until just now!
Sam
Ah! OK. :-) We all learn from errors (even those of other people!).
PhiLho
I think it's text/xhtml that IE 6 has a problem with; I've never played with it, but I've heard many complaints about it. I believe that IE 6 will simply not work if you send text/xhtml, but I'm not sure.
dirtside
One type IE has problems with is XHTML, which is application/xhtml+xml or application/xml -- IE does not render XHTML sent with either of these correct content-types (you can incorrectly send as text/html to force IE to use its HTML mode, but this is wrong and can cause other side effects).
joelhardi