Wrong thread. Bob S
> On Jul 21, 2015, at 13:17 , David Bovill <david@viral.academy> wrote: > > I want to send gzip encoded data back from the LiveCode server I'm working > on. According to the docs: compress function uses the slob compression > library. > > And according to Wikipedia > > >> The "Content-Encoding"/"Accept-Encoding" and "Transfer-Encoding"/"TE" >> headers in HTTP <https://en.m.wikipedia.org/wiki/HTTP>/1.1 allow clients >> to optionally receive compressed HTTP >> <https://en.m.wikipedia.org/wiki/HTTP_compression> responses and (less >> commonly) to send compressed requests. The specification for HTTP/1.1 (RFC >> 2616 <https://tools.ietf.org/html/rfc2616>) specifies three compression >> methods: "gzip" (RFC 1952 <https://tools.ietf.org/html/rfc1952>; the >> content wrapped in a gzip stream), "deflate" (RFC 1950 >> <https://tools.ietf.org/html/rfc1950>; the content wrapped in a >> zlib-formatted stream), and "compress" (explained in RFC 2616 >> <https://tools.ietf.org/html/rfc2616> section 3.5 as "*The encoding >> format produced by the common UNIX file compression program compress. This >> format is an adaptive Lempel-Ziv-Welch coding (LZW).*"). Many client >> libraries, browsers, and server platforms (including Apache >> <https://en.m.wikipedia.org/wiki/Apache_HTTP_Server> and Microsoft IIS >> <https://en.m.wikipedia.org/wiki/Microsoft_IIS>) support gzip. Many >> agents also support deflate, although several important players incorrectly >> implement deflate support using the format specified by RFC 1951 >> <https://tools.ietf.org/html/rfc1951> instead of the correct format >> specified by RFC 1950 <https://tools.ietf.org/html/rfc1950> (which >> encapsulates RFC 1951 <https://tools.ietf.org/html/rfc1951>). Notably, >> Internet Explorer versions 6, 7, and 8 report deflate support but do not >> actually accept RFC 1950 <https://tools.ietf.org/html/rfc1950> format, >> making actual use of deflate highly unusual. Many clients accept both RFC >> 1951 <https://tools.ietf.org/html/rfc1951> and RFC 1950 >> <https://tools.ietf.org/html/rfc1950>-formatted data for the "deflate" >> compressed method, but a server has no way to detect whether a client will >> correctly handle RFC 1950 <https://tools.ietf.org/html/rfc1950> format. >> > > That bodes well. Anyone know if this works with most browsers? > _______________________________________________ > use-livecode mailing list > use-livecode@lists.runrev.com > Please visit this url to subscribe, unsubscribe and manage your subscription > preferences: > http://lists.runrev.com/mailman/listinfo/use-livecode _______________________________________________ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode