Martin Marques wrote:
Thomas Bruederli wrote:
I'll check that and add a fallback to text/plain.
Could the fallback be for badly written content-type headers too?
If you do, please make sure you only fall-back to text/plain if the "badly written" Content-Type header element starts with "text/". That would be in agreement with the MIME RFC, which mandates that an unknown subtype of "text" should be treated as text/plain.
Bob