Closed michaelrsweet closed 18 years ago
CUPS.org User: mike
One problem with adding more fields to the current array is that it will break binary compatibility, which is a show-stopper on MacOS. We're looking at ways to extend things in 1.2 that won't break binary compatibility but allow you to get/set arbitrary fields... The 1.1.19 changes to add Expect and Cookie/SetCookie support are an example of how we made changes that wouldn't break binary compatibility.
FWIW, the Content-Disposition header is not standard HTTP but an extension which is referenced in RFC 2616 and documented in RFC 2183...
CUPS.org User: mike
We have decided to not support the Content-Disposition header - we currently have no need for it in CUPS, and adding the header will require a lot of changes.
It is conceivable that a future release will add support for arbitrary fields, however it won't be CUPS 1.2...
Version: -feature CUPS.org User: speter.codehost
I am using the CUPS HTTP API for some basic client stuff, and it is sometimes useful to access the content of that header (for instance, to get the filename of a file being downloaded).
It is trivial to add support for it in the HTTP API, so it would be nice to have it in the official tree.