I am evaluating Adobe AIR's HTML component and trying to figure out what is supported.
I built the AIR app and had it point to www.google.com
I notice that the requests to fetch JS,CSS from Adobe AIR do not include Accept-Encoding: gzip header.
Does Adobe AIR's HTML Component support Accept-Encoding : gzip header ?
I also noticed that even though the content served with far futures expiry, i.e. has Cache-Control: maxage={value} subsequent requests are being made and content is not served from the browser's cache.
I observed this accross the app restarts.
Can someone please clarify support of the two above Http headers ?
Thank you.
-Prashant
Here is the screenshot of Charles which captures request to the goolge's logo that is being sent again even though it had max-age of 365 days in the previous response. Observe the two requests which got a 304 respone, I expected the GET request to the logo to be not made at all and content be served from the browser' cache.
Going to see if someone who's familiar with the webkit portion of AIR can respond. Gzip should be supported from AIR 2.03 forward (http://blogs.adobe.com/simplicity/2010/08/an-update-on-http-content-en coding-in-air-applications.html).
Chris
You might also want to check out the useCache property to see if this helps. See these links:
http://forums.adobe.com/thread/726573
http://forums.adobe.com/thread/490497
http://help.adobe.com/en_US/FlashPlatform/reference/actionscript/3/fla sh/html/HTMLLoader.html
Thank you for taking time to look into this.
Yes, GZip in Content-Encoding header seems to be passed when used AIR 3.
Setting useCache does not have impact on the behavior i originally reported. When the AIR application restarts HTTP requests whose responses have Cache-Control : maxage headers are re-requested. If these requests had returned Last-Modified header the re-requests are conditional GETs and get 304. But even making these conditional GET requests is unneccessary and the AIR application startup experience will be better without them.
Would you mind entering this as a bug over at bugbase.adobe.com? Please post back with the bug number and I'll forward along internally.
Thanks,
Chris
If you want this bug fixed, please vote for it here : https://bugbase.adobe.com/index.cfm?event=bug&id=3301204
North America
Europe, Middle East and Africa
Asia Pacific