HTTPResponse too strict with text mime-types

[Andrew Mustun]

In zope.publisher.http.HTTPResponse:

def _implicitResult(self, body):
    ...
    if not content_type.startswith('text/'):
        raise ValueError(
            'Unicode results must have a text content type.')
    ...
    content_type += ';charset=%s' %encoding
    ...

IMHO, the content type test here is much too strict.
Many mime types don't start with 'text/' and are still text mime types. E.g. application/xml, application/xhtml+xml.

To my best knowledge those mime types can also have a charset parameter appended. E.g. 'application/xml; charset=UTF-8'.

Unfortunately, I couldn't find the reference documentation about that or a definitive list of mime types that can have a charset parameter, so this needs some further research..

Andrew

[Marius Gedminas (mgedmin)]

This is a duplicate of http://www.zope.org/Collectors/Zope3-dev/668

[Gary Poster (gary)]

zope.mimetype keeps track of this information, fwiw. http://svn.zope.org/zope.mimetype/trunk/src/zope/mimetype . It could be used for this kind of check: it keeps track of what mimetypes are encodable.

[Colin Watson (cjwatson)]

The zope.publisher project on Launchpad has been archived at the request of the Zope developers (see https://answers.launchpad.net/launchpad/+question/683589 and https://answers.launchpad.net/launchpad/+question/685285). If this bug is still relevant, please refile it at https://github.com/zopefoundation/zope.publisher.