pitz wrote:
As part of a "file" submission/upload, the browser encodes the file in base64 and includes the encoded portion as part of the HTTP POST. The encoded portion is also "tagged" with a filename (the same file name that the user selected from his local drive). Only the filename, and not the full path, is included in the tag -- so the HTTP server is free to save it off into any folder it wishes to, and it also does not have to use the filename included in the tag.
Ah! So I had it 50% correct initially. To see if I have this correct: binary transfer from server to browser does not require encoding. Transfer from browser to server _does_ require MIME encoding.