IETF 80 - Content-Disposition Julian Reschke, greenbytes Julian - - PowerPoint PPT Presentation

▶
ietf 80 content disposition
SMART_READER_LITE
LIVE PREVIEW

IETF 80 - Content-Disposition Julian Reschke, greenbytes Julian - - PowerPoint PPT Presentation

Sep 02, 2022 315 likes •360 views

IETF 80 - Content-Disposition IETF 80 - Content-Disposition Julian Reschke, greenbytes Julian Reschke, greenbytes 1 IETF 80 - Content-Disposition Problem Statement As of recent, there was no interop for non-ASCII filenames in

slide-1
SLIDE 1

IETF 80 - Content-Disposition

Julian Reschke, greenbytes

IETF 80 - Content-Disposition Julian Reschke, greenbytes 1

slide-2
SLIDE 2

Problem Statement

  • As of recent, there was no interop for non-ASCII filenames in

Content-Disposition header fields. See http://greenbytes.de/tech/ tc2231/ for the ugly details.

  • There was confusion about who is defining what (RFC 2616 vs RFC

2183).

  • RFC 2183 contains complicated options that do not make sense in

HTTP.

IETF 80 - Content-Disposition Julian Reschke, greenbytes 2

slide-3
SLIDE 3

Thus...

  • Define in separate spec from the two above, clarifying I18N,

removing options, fixing bugs.

  • Approved <blink>2011-03-28</blink>.
  • Firefox, Opera, and Konqueror did implement this for a long time.
  • Chrome 9 and IE 9 followed since IETF LC.
  • Only one major UA left (just saying).

IETF 80 - Content-Disposition Julian Reschke, greenbytes 3

slide-4
SLIDE 4

Why six months between IETF LC and now?

  • Some UA vendors wanted to discuss error handling.
  • Turns out that in this case, error handling was inconsistent.

Next steps

  • Reference from HTTPbis specs?
  • Advance to Draft Standard soon?

IETF 80 - Content-Disposition Julian Reschke, greenbytes 4