[1222] | 1 | <!DOCTYPE html
|
---|
| 2 | PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
|
---|
| 3 | <html xmlns="http://www.w3.org/1999/xhtml">
|
---|
| 4 | <head>
|
---|
| 5 | <title>IETF 80 - Content-Disposition</title>
|
---|
| 6 | <style type="text/css">
|
---|
| 7 | body {
|
---|
| 8 | color: black;
|
---|
| 9 | font-family: verdana, helvetica, arial, sans-serif;
|
---|
| 10 | font-size: 18pt;
|
---|
| 11 | }
|
---|
| 12 | h1 {
|
---|
| 13 | font-size: 36pt;
|
---|
| 14 | }
|
---|
| 15 | li {
|
---|
| 16 | margin-top: 0.5em;
|
---|
| 17 | }
|
---|
| 18 | q {
|
---|
| 19 | font-style: italic;
|
---|
| 20 | }
|
---|
| 21 | del {
|
---|
| 22 | color: red;
|
---|
| 23 | text-decoration: line-through;
|
---|
| 24 | }
|
---|
| 25 | ins {
|
---|
| 26 | color: green;
|
---|
| 27 | text-decoration: underline;
|
---|
| 28 | }
|
---|
| 29 | .break {
|
---|
| 30 | page-break-before: always;
|
---|
| 31 | }
|
---|
| 32 | @page {
|
---|
| 33 | size: a4 landscape;
|
---|
| 34 | }
|
---|
| 35 | @page {
|
---|
| 36 | @bottom-left {
|
---|
| 37 | content: "Julian Reschke, greenbytes";
|
---|
| 38 | }
|
---|
| 39 | @bottom-right {
|
---|
| 40 | content: counter(page);
|
---|
| 41 | }
|
---|
| 42 | @top-center {
|
---|
| 43 | content: "IETF 80 - Content-Disposition";
|
---|
| 44 | }
|
---|
| 45 | }
|
---|
| 46 | </style>
|
---|
| 47 | </head>
|
---|
| 48 | <body>
|
---|
| 49 | <h1>IETF 80 - Content-Disposition</h1>
|
---|
| 50 | <p>
|
---|
| 51 | <a href="mailto:julian.reschke@greenbytes.de">Julian Reschke</a>, greenbytes
|
---|
| 52 | </p>
|
---|
| 53 |
|
---|
| 54 | <h2 class="break">Problem Statement</h2>
|
---|
| 55 | <ul>
|
---|
| 56 | <li>As of recent, there was no interop for non-ASCII filenames in
|
---|
| 57 | Content-Disposition header fields. See <a href="http://greenbytes.de/tech/tc2231/">http://greenbytes.de/tech/tc2231/</a> for the ugly details.</li>
|
---|
| 58 | <li>There was confusion about who is defining what (RFC 2616 vs RFC 2183).</li>
|
---|
| 59 | <li>RFC 2183 contains complicated options that do not make sense in HTTP.</li>
|
---|
| 60 | </ul>
|
---|
| 61 |
|
---|
| 62 | <h2 class="break">Thus...</h2>
|
---|
| 63 | <ul>
|
---|
| 64 | <li>Define in separate spec from the two above, clarifying I18N, removing options, fixing bugs.</li>
|
---|
| 65 | <li>Approved <tt><blink></tt>2011-03-28<tt></blink></tt>.</li>
|
---|
| 66 | <li>Firefox, Opera, and Konqueror did implement this for a long time.</li>
|
---|
| 67 | <li>Chrome 9 and IE 9 followed since IETF LC.</li>
|
---|
| 68 | <li>Only one major UA left (just saying).</li>
|
---|
| 69 | </ul>
|
---|
| 70 |
|
---|
| 71 | <h2 class="break">Why six months between IETF LC and now?</h2>
|
---|
| 72 | <ul>
|
---|
| 73 | <li>Some UA vendors wanted to discuss error handling.</li>
|
---|
| 74 | <li>Turns out that in this case, error handling was inconsistent.</li>
|
---|
| 75 | </ul>
|
---|
| 76 |
|
---|
| 77 | <h2>Next steps</h2>
|
---|
| 78 | <ul>
|
---|
| 79 | <li>Reference from HTTPbis specs?</li>
|
---|
| 80 | <li>Advance to Draft Standard soon?</li>
|
---|
| 81 | </ul>
|
---|
| 82 |
|
---|
| 83 | </body>
|
---|
| 84 | </html>
|
---|