Ultrashock Forums - View Single Post - GZip compression + Flash Player + IE6 = Nightmare

Polaco · 2008-11-12 #7

Hi Nutrox!

We have continued looking at the problem, we have found that the IIS was using an old version of the ISAPI dll files that comes with BEA Weblogic 8.1, this dlls were changing the response in some way and compressing it with gzip.
The replaced files were:

iisforward.dll
iisproxy.dll

So with the old files the response header was:

Response:HTTP/1.1 200 OK
Cache-Control:no-cache
Connection:close
Date:Wed, 12 Nov 2008 12:20:33 GMT
Conten-Type:text/html; charset=ISO-8859-1
Server:Miscrosoft-IIS/6.0
X-Powered-By:ASP.NET
X-Vignette-RespondedWith:AJAX
Content-Encoding:gzip
Vary:Accept-Encoding
Transfer-Encoding:chunked

and with the new ones:

Response:HTTP/1.1 200 OK
Content-Type: text/html;charset=ISO-8859-1
X-Vignette-RespondedWith:AJAX
Transfer-Encoding:chunked
Cache-Control:no-cache

So now, if we want to compress the data with gzip we must do it from the servlet and we are sure that the response will be compressed data, and so build our swf to behave acordingly ( as you stated that I should know the incoming data format).

mmm this makes me willing to do some experimetns to try to gzip data and send it to flash.
Also some new doubts has arisen..
If the browser should decompress the gzipped data, has sense to wait for a binary response? Can flash specify when wants the response compressed or not and the browser then will not uncompress it?
What will happen if incoming compressed text uses the is ISO-8859-1 charset and not UTF ?
Will "data.readUTFBytes( data.length )" work properly?
Is it posible to compress a Value Object in AMF format and send it to flash and then use myByteArray.readObject() to uncompress it and bind it to an AS3 object without using Blaze or things like that?

thanks a lot for your support Nutrox!
Awesome as always

Polaco.

	Polaco	2008-11-12 #7
	Hi Nutrox! We have continued looking at the problem, we have found that the IIS was using an old version of the ISAPI dll files that comes with BEA Weblogic 8.1, this dlls were changing the response in some way and compressing it with gzip. The replaced files were: iisforward.dll iisproxy.dll So with the old files the response header was: Response:HTTP/1.1 200 OK Cache-Control:no-cache Connection:close Date:Wed, 12 Nov 2008 12:20:33 GMT Conten-Type:text/html; charset=ISO-8859-1 Server:Miscrosoft-IIS/6.0 X-Powered-By:ASP.NET X-Vignette-RespondedWith:AJAX Content-Encoding:gzip Vary:Accept-Encoding Transfer-Encoding:chunked and with the new ones: Response:HTTP/1.1 200 OK Content-Type: text/html;charset=ISO-8859-1 X-Vignette-RespondedWith:AJAX Transfer-Encoding:chunked Cache-Control:no-cache So now, if we want to compress the data with gzip we must do it from the servlet and we are sure that the response will be compressed data, and so build our swf to behave acordingly ( as you stated that I should know the incoming data format). mmm this makes me willing to do some experimetns to try to gzip data and send it to flash. Also some new doubts has arisen.. If the browser should decompress the gzipped data, has sense to wait for a binary response? Can flash specify when wants the response compressed or not and the browser then will not uncompress it? What will happen if incoming compressed text uses the is ISO-8859-1 charset and not UTF ? Will "data.readUTFBytes( data.length )" work properly? Is it posible to compress a Value Object in AMF format and send it to flash and then use myByteArray.readObject() to uncompress it and bind it to an AS3 object without using Blaze or things like that? thanks a lot for your support Nutrox! Awesome as always Polaco.