masinter multipart-form-data issues

masinter / multipart-form-data

update to RFC 2388 definition of multipart/form-data

8 stars 6 forks source link

issues

Newest

Newest Most commented Recently updated Oldest Least commented Least recently updated

Conversion tool not working for TEXT and HTML

#23 lfaoro opened 6 years ago
0
move Section 1 into a note, add metadata, avoid TABs in artwork

#22 reschke closed 9 years ago
0
update HTML5 reference

#21 reschke closed 9 years ago
0
Some typo fixes.

#20 Electron-libre closed 10 years ago
0
remove normative text from appendix

#19 masinter opened 10 years ago
0
original request

#18 masinter opened 10 years ago
0
What's the holdup?

#17 annevk opened 10 years ago
1
Content-Transfer-Encoding

#16 peteroupc closed 10 years ago
7
Comments from Dave Thaler

#15 dthaler closed 10 years ago
1
Form generation and python support

#14 plehegar closed 10 years ago
1
Forced UTF-8 encoding on the HTTP POST response

#13 plehegar closed 10 years ago
0
Minor tweaking

#12 darobin closed 11 years ago
0
clarify that sender must determine proper content-type, using local file system conventions and/or sniffing

#11 masinter closed 10 years ago
1
Comments from Leigh Klotz

#10 masinter closed 10 years ago
1
comments from Alexey

#9 masinter closed 10 years ago
1
enumerate how current clients encode non-ascii fields and values

#8 masinter closed 11 years ago
1
clarify that restricting to ASCII fieldnames

#7 masinter closed 11 years ago
1
multipart/mixed usage recommend NOT

#6 masinter closed 11 years ago
1
clarify "can" in 3.2

#5 masinter closed 11 years ago
2
example error needs empty line

#4 masinter closed 11 years ago
1
Appendix B unnecessary

#3 masinter closed 11 years ago
1
html references wrong

#2 masinter closed 11 years ago
1
what do do about non-ASCII field names

#1 masinter closed 11 years ago
1