search

rolkey / indyproject

Automatically exported from code.google.com/p/indyproject
0 stars 0 forks source link

Support RFC 2183 rules when parsing Content-Disposition headers #97

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
Current logic applies RFC 822 syntax rules when parsing Content-
Disposition email headers.  RFC 2183 updates the definition of Content-
Disposition to use RFC 2045 syntax rules.  This affects how various values 
need to be handled, such as when the 'filename' parameter contains an 
unquoted value - illegal under RFC 822 but valid under RFC 2045.

Original issue reported on code.google.com by gambit47 on 8 May 2010 at 12:02

GoogleCodeExporter commented 8 years ago

Original comment by gambit47 on 12 May 2010 at 12:44