The content-type header could do with some server-side filtering, right now it's stored as is which causes this: 
just lowercasing it all and then stripping out charset and ending semicolon would be cool. Perhaps storing the charset in a separate variable would be nice too :)
The content-type header could do with some server-side filtering, right now it's stored as is which causes this:
just lowercasing it all and then stripping out charset and ending semicolon would be cool. Perhaps storing the charset in a separate variable would be nice too :)