I am using an UrlLoader to load several things, mostly JSON but also (user-uploaded) images sometimes.
However, the following URL triggers the Event.ERROR listener, whilst it opens just fine in a regular browser:
https://cdn.chainels.com/image/?disp=1&CID=111349965282403244&id=91381324578234817Moreover, when using a localhost set-up (exactly the same but uses
http://localhost/image....) this all still works. Other requests (that use
https://www.chainels.com instead of
https://cdn.chainels.com though) work anyway.
How can I even debug this without any extra information in the error event listener?
Comments
Does setting UserAgent header change the behavior?
For debugging these types of networking issues, on Mac I use Charles Proxy (paid tool) http://www.charlesproxy.com and on Windows I use the free Fiddler Tool. http://fiddler2.com
Hope this helps,
- Ian
@ar2rsawseen I use the latest version (2013.06.3 on Windows). It is also not purely HTTPS related. Let me make it clear:
- fails: https://cdn.chainels.com/image/?disp=1&CID=111349965282403244&id=91381324578234817
- works: http://localhost/image/?disp=1&CID=111349965282403244&id=91381324578234817
- works: https://www.chainels.com/ajax/journal/?action=rawpages
It seems like fetching data-files (content-disposition and content-type headers set) through https fails, whilst fetching json through https succeeds.
The used certificate on chainels.com is a wildcard one; perhaps a check for this is failing (as localhost invalid certificate makes it fail as well)?
Again with an APK on Android, everything works fine again.
Edit: I use { ["Content-Type"] = "application/x-www-form-urlencoded", ["User-Agent"] = "Gideros" } for each request. Leaving content-type or everything away or something does not do anything concerning this issue.
Edit2: note that the ajax URL is missing a log-in token for obvious security reasons
But yes, UrlLoader is something that is implemented specifically for each platform, thus there might be difference between Desktop and Mobile platform versions