Copy link to clipboard
Copied
I've been tracking down a bug that has cropped up in both my existing air applications and new applications. My applications are javascript/html based adobe air applications.
When I test my adobe air application using Dreamweaver CS5 the application XHR calls work fine. When I compile them and run the air application the calls stop working.
I can see the call going to out returning with the correct response (200) with the valid information but the air application now returns a status of 0 every single time. The only different I can see is that the header file now contains Accept-Encoding: gzip,deflate which it does not in the preview of the adobe air application.
I have tried adding my own accept-encoding using setRequestHeader and it is ignored.
A full log of the messages, returned, values, etc are in this forum post: http://forums.adobe.com/thread/705524?tstart=0
The recent release notes for 2.03 ( http://www.adobe.com/support/documentation/en/air/2_0_3/releasenotes_developers.html ) indicate that this is a recently added feature and that the gzip,deflate is added by default.
I need to find a way either to fix the reason for the status code 0 being returned when I can see the call succeeding using Fiddler2 (a trace program) or find a way to over-ride this value.
Copy link to clipboard
Copied
os is windows 7, 64bit.
Copy link to clipboard
Copied
Thanks for bringing this to our attention. I've forwarded this along to the developers that implemented the compression feature. We'll take a look at let you know what we find ASAP.
Chris
Copy link to clipboard
Copied
As a follow up, I updated the line:
<application xmlns="http://ns.adobe.com/air/application/2.0">
in my application.xml to:
<application xmlns="http://ns.adobe.com/air/application/1.5">
And the application began to work again.
So it is something with the latest release that is causing issues.
Copy link to clipboard
Copied
I've tried to reproduce your problem but without any help. Using the code snippet that you have provided in another forum post I've created an app that makes a request to resource that is then served compressed.
Is there any possibility to create a small test app that can reproduce this issue using a public url? If not can you create us a test account that we can use for testing?
The "Accept-Encoding" header cannot be set / or overwritten from javascript when using the XMLHttpRequest object due to security restrictions (http://www.w3.org/TR/XMLHttpRequest/#dom-xmlhttprequest-setrequestheader).
Regards,
-Catalin
Copy link to clipboard
Copied
I can create a test app for you that'll use the same interfaces I'm using. It is public but you'll have to sign up for 1 service, which is free to
sign up for.
I can provide more information through email if you could provide me with a way to contact you outside of the forum posts...
Casey
Copy link to clipboard
Copied
Hi Casey,
You can write me on my email address: canastas@adobe.com
Regards,
-Catalin
Copy link to clipboard
Copied
Hi Casey,
I've investigated your issue and discovered that this is an actual bug related to the http compression feature on Windows platforms. I've reported it (internal bug id #2716077) and sent it to review and approval. I will let you know when will it be fixed.
Thank you for reporting it and we apologies for any inconvenience produced by this issue.
Regards,
-Catalin
Copy link to clipboard
Copied
Thank you for the update. I appreciate you taking the time to look
into this for me.
I look forward to hearing when it'll be fixed.
Casey
Copy link to clipboard
Copied
Just curious if a date has been associated with the bug fix yet?
Thanks,
Casey
Copy link to clipboard
Copied
Hi Casey,
The bug has been fixed and will be in AIR 2.5 release due later this year.
Cheers,
Raul
Copy link to clipboard
Copied
Hi,
Is this definitely fixed in 2.5? I changed my namespace from 1.5 to 2.5 and seemed to have the same issue.
I had to change back to 1.5.
Thanks
Message was edited by: heratech. typo
Copy link to clipboard
Copied
Hi,
Can you try to reproduce the issue with a small test app and send it to us?
I have retested this bug fix and using our testing app it appears to be fixed.
Regards,
Catalin