-
1. Re: Very slow response time with URLLoader on iOS 8
Pravendra Oct 9, 2014 3:50 AM (in response to Pierre Yves GATOUILLAT)Thanks for reporting the issue.
I have tried to reproduce this issue, but it is not reproducible at my end. It may depend on Network speed and File Size.
Could you please provide a sample app for this.
-Pravendra
-
2. Re: Very slow response time with URLLoader on iOS 8
Pierre Yves GATOUILLAT Oct 9, 2014 6:41 AM (in response to Pravendra)Actually it seems more prevalent with our web service on Google App Engine. I can't provide the url, but we can repro with this one: https://testfor367.appspot.com/ for example. It seems all https appspot.com subdomains are affected. We're currently looking for other urls with the same defect, and also trying to know if this has something to do with https or not...
-
3. Re: Very slow response time with URLLoader on iOS 8
Pierre Yves GATOUILLAT Oct 10, 2014 11:34 AM (in response to Pravendra)That's it, no problem with http, but a slow response time with https. So I guess this is an issue between AIR, iOS 8 and the process to secure the http protocol on appspot.com.
-
4. Re: Very slow response time with URLLoader on iOS 8
Pierre Yves GATOUILLAT Oct 10, 2014 11:41 AM (in response to Pravendra)It seems linked to the size of the sent or received payload, so bandwidth related. However that's not comparable to a regular bandwidth issue. For example if I send a 10KB payload with HTTP, no problem, it's done in two hundred milliseconds or so. But the same request with the same 10KB payload in HTTPS will take up to 20 seconds to get an answer. But a request with only a few bytes of payload in HTTPS will get an answer in a second or so. And this issue happens only on iOS 8.
Please let me know if you're still unable to reproduce. It's just a simple project with an URLLoader. We tested on both AIR 14 and 15.
-
5. Re: Very slow response time with URLLoader on iOS 8
Pravendra Oct 13, 2014 12:26 AM (in response to Pierre Yves GATOUILLAT)I have tried to reproduce the issue using below code snippet:
var loader:URLLoader = new URLLoader();
configureListeners(loader);
var request:URLRequest = new URLRequest("https://testfor367.appspot.com//");
try {
loader.load(request);
} catch (error:Error) {
trace("Unable to load requested document.");
}
But I am not seeing any difference on loading the data in iOS 7 and 8 devices.
data is loaded within 2 seconds.
-Pravendra
-
6. Re: Very slow response time with URLLoader on iOS 8
Pierre Yves GATOUILLAT Oct 13, 2014 1:46 AM (in response to Pravendra)Could you try adding:
var bytes : ByteArray = new ByteArray();
for(var k : int = 0 ; k < 2048 ; k++)
bytes.writeUnsignedInt(0xFFFFFFFF * Math.random());
var variables : URLVariables = new URLVariables();
variables["payload"] = Base64.encode(bytes);
request.data = variables;
Just to have a little random payload.
Thanks.
-
7. Re: Very slow response time with URLLoader on iOS 8
Pravendra Oct 13, 2014 5:04 AM (in response to Pierre Yves GATOUILLAT)I have added above payload code into my code snippet and getting the below error on debugging the code:
progressHandler loaded:273 total: 273
httpStatusHandler: [HTTPStatusEvent type="httpStatus" bubbles=false cancelable=false eventPhase=2 status=400 redirected=false responseURL=null]
ioErrorHandler: [IOErrorEvent type="ioError" bubbles=false cancelable=false eventPhase=2 text="Error #2032: Stream Error. URL: https://testfor367.appspot.com/?payload=8dgzb2qLiyXtEdtpf1......." errorID=2032]
-
8. Re: Very slow response time with URLLoader on iOS 8
Pierre Yves GATOUILLAT Oct 13, 2014 10:04 AM (in response to Pravendra)Did you debug this directly on iOS 8? Do you have the same result on iOS 7? Because we sometimes have stream errors like that when the request takes too much time to complete. As you can see, the URL is alive on a desktop browser, so you shouldn't have this stream error.
In this case, reducing the payload could help notice the slow response time and avoid the stream error.
-
9. Re: Very slow response time with URLLoader on iOS 8
Pierre Yves GATOUILLAT Nov 3, 2014 6:42 AM (in response to Pierre Yves GATOUILLAT)Issue still reproducible on iOS 8.1


