#141: Optionally supply a charset to go with the content type ------------------------+--------------------------------------------------- Reporter: nick | Owner: nick Type: defect | Status: new Priority: normal | Milestone: Component: openguides | Version: svn Severity: normal | Keywords: ------------------------+--------------------------------------------------- We should allow guides to set a charset, which gets included with the content type.
Otherwise, a default (normally ISO-8859-1) is often added, which screws things up (eg your data isn't sent as UTF-8, and then postgres gets in a huff)
#141: Optionally supply a charset to go with the content type ------------------------+--------------------------------------------------- Reporter: nick | Owner: nick Type: defect | Status: closed Priority: normal | Milestone: Component: openguides | Version: svn Severity: normal | Resolution: fixed Keywords: | ------------------------+--------------------------------------------------- Changes (by nick):
* resolution: => fixed * status: new => closed
Comment:
(In [868]) Support the config flag http_charset, which sets a http charset header on content type. (Closes #141)
openguides-tickets@lists.openguides.org