Content-Disposition HTTP response header

[Angus Robertson 612]

ICS has always supported the Content-Disposition: form-data header for POSTing files, but seems to bypassed Content-Disposition as a HTTP response header, declaring content as inline or attachment with a file name so it can be saved.  We tend to look at Content-Type to determine if content should be saved.

 

So I plan to add web server support to send Content-Disposition: inline and Content-Disposition: attachment, and client support to parse the header and file name.

 

But also wondering whether Content-Disposition should be sent as a request header when POST/PUTing a single file as binary, to avoid needing to base64 encode it within form-data, which is a major overhead for gigabyte sized uploads.  Actually easy to add to the REST component that already has such an upload and the web server samples that save such data, but taking the file name from a URL parameter.

 

Done a little Googling, but can not see any official use of Content-Disposition as a request header, maybe I missed something?

 

Any thoughts, is it worth adding to ICS?

 

Angus