This is a list of potentially interesting CMSs / CRMs / Web frameworks / libraries for implementation of RFC6266.

We should try to identify affected code (ideally with a link to source(s)) for each, as well as the public bug database for each. Eventually we'll raise a *polite* bug where necessary.

Python

• stdlib
  • ​i18n in email headers (often used for HTTP too)
  • ​some related utilities
  • ​mimetools.Message - default for the built-in HTTP server. Subclass of ​rfc822.Message.
• ​Django - nothing in Django itself. However:
  • ​snippet showing how to do it (see also links at bottom)
  • ​docs
  • ​outputting PDFs
  • ​dodgy-looking ticket where everything is unicode
• Zope
  • ​relevant bug
• Plone
  • ​utils.py:contentDispositionHeader() - uses stdlib email.Message
  • ​ticket 8591

Ruby

• stdlib
  • ​Net:HTTPHeader doesn't seem to
  • ​source; note other things below, seems a reasonable place to integrate
• ​Rails
  • ​streaming.rb:send_file_headers
  • ​response.rb looks like something should go here
• ​Merb
  • ​controller.rb (and elsewhere in file) - nothing for i18n
• ​Sinatra
  • ​base.rb - nothing for i18n.

Node.JS

• stdlib
  • ​http.js - nothing

PHP

• stdlib
• Drupal
• symfony
• Zend
• mediawiki
• SugarCRM

Java

• stdlib
  • doesn't address HTTP header fields
• Servlet API
  • no specific support for Content-Disposition
• GWT
• cocoon
• tapestry
• sling
• spring
• Jersey (JAX-RS)

Perl

• LWP
• mason
• twiki
• scoop
• slash
• movable type

ASP.NET