Skip to main content
Jul 31, 2012 5:41 AM UTC
Answered

Cache-Control and Accept-Encoding support in Adobe AIR HTML Component

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

This topic is closed to new replies. Start a new post to keep the conversation going.
Correct answer
Jan 23, 2013 1:03 PM UTC

Bug Number : 3301204


If you want this bug fixed, please vote for it here : https://bugbase.adobe.com/index.cfm?event=bug&id=3301204

9 replies

Jul 31, 2012 6:10 AM UTC

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.

Translate
chris.campbell
Legend
Aug 1, 2012 12:15 AM UTC

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-encoding-in-air-applications.html).

Chris

Translate
chris.campbell
Legend
Aug 1, 2012 1:02 AM UTC