Bizarre Content-Type Problems

I’ve been having some really weird problems with my mime types lately, which has put a hamper on some of the RSS and standards compliance stuff I want to do here. Every document generated by PHP was being sent with a Content-Type: text/html; encoding: iso-8859-1; regardless of whatever was being specified with header in the code. I’m still not entirely clear on what fixed it, but I believe it had something to do with no default content type being specified in the php.ini file, but a default encoding specified. This confused things somewhere and it’s all resolved now. There is the default content type of text/html which works for 99% of stuff, and the overrides now work for the rest. Now I can rest easy.

One thought on “Bizarre Content-Type Problems

  1. I have a problem with content type.
    I am storing the an ” oppen Office document ” in oracle data base . and am i am also diaplaying
    the data or documents from data base on the browser .i got the results for all files except
    “oppen office document ”
    any one can help me

SHARE YOUR THOUGHTS