Re: Marinetti 'casper' - How do I use it?

["geoff" <geoff@a2central.com.remove-r52-this>]

  To: Steven Hirsch
No, there is no reason to encode data that is being uploaded to the server. 
See RFC 1867, http://www.faqs.org/rfcs/rfc1867.html .  The file contents can 
be sent as straight binary.  What is accurate is to say that file uploads 
follow the MIME multipart data stream.

Fully compliant modern mail servers and mail clients can handle non-encoded 
MIME multipart data streams for email too.  But, this is generally not done 
for compatibility with older systems.

Geoff

 > 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.

 > --- Synchronet 3.14a-Win32 NewsLink 1.85
--- Synchronet 3.14a-Win32 NewsLink 1.85
A2Central.com - Your total source for Apple II computing.