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

[pitz <pitz.wong@gmail.com>]

That's my understanding as well.  The HTTP server will have to encode
binary data in some MIME format before sending it back to the
browser.  I've read somewhere about an HTTP-ng that allows binary
transport over the wire, but MIME-encoding is still standard on
regular HTTP.

Steven Hirsch wrote:
> Jeff Blakeney wrote:
>
> >> There's a difference between spitting back a static web page preceeded by HTTP
> >> headers and being able to transfer a binary file.  The latter requires
> >> encoding and decoding the last I looked.
> >
> > Anything sent via HTTP will have HTTP headers.  That is part of the
> > HTTP.  If you send data without those headers, you are no longer sending
> > via HTTP anymore.  There is also no encoding done by an HTTP server.
> > Encoded data can be transfered but it is never encoded by the HTTP
> > server unless you are talking about an HTTPS server which does do some
> > encoding for security but that is a different transfer protocol.
> >
> > You mentioned MIME in another post but that has absolutely nothing to do
> > with HTTP.  MIME is an encoding method that can be transferred in many
> > ways but is most popular in e-mail.
>
> I don't do enough web coding to argue the point, but I thought the standard
> dictated 7-bit ASCII and that MIME encoding was required.  I have been wrong
> before and may well be mistaken about this.