I have the following HTTPService defined:
<mx:HTTPService id="youTubeHttpService" result="resultHandler(event)" fault="faultHandler(event)"/>
And I'm using the following URL (pattern) to obtain a list of YouTube videos for a particular user:
http://gdata.youtube.com/feeds/api/users/Y/uploads
where Y is a registered user on YouTube.
Eg: http://gdata.youtube.com/feeds/api/users/YouTube/uploads
I send an HTTP request using the following syntax:
youTubeHttpService.url = "http://gdata.youtube.com/feeds/api/users/YouTube/uploads";
youTubeHttpService.resultFormat = "object";
youTubeHttpService.send();
Now, the above code works fine for some people using our software while others are experiencing the following error ( in faultHandler() ):
Error: [RPC Fault faultString="Security error accessing url" faultCode="Channel.Security.Error" faultDetail="Destination: DefaultHTTP"]
Again, the error happens to some people and not for others.
Have I missed something? Would it be a machine / browser specific problem? As a sanity check the above code works with the same .swf file in chrome, ie, firefox and safari.
I have read about the crossdomain.xml and don't think that is the issue as YouTube have that defined.
Finally, all users (intranet app) are using IE and the same version of flash.
Any help would be greatly appreciated as I have been pulling my hair out the past 2 days and asking the question over and over again "Why is it only happening for some users and not for other users?"
Norm.
Could it be possible that they have their security settings too high? Check out this page to change them http://www.macromedia.com/support/documentation/en/flashplayer/help/settings_manager04.html
You have a crossdomain policy restriction
http://gdata.youtube.com/crossdomain.xml
It looks like youTube is allowing pretty much most everything.
So that leads me to believe the file is not being loaded.
Try this or a form of it.
Security.allowDomain( 'gdata.youtube.com' );
Security.loadPolicyFile( 'gdata.youtube.com' );
Also Use HTTPFox plugin for FireFox to see if it gets loaded
If worse comes to worse try this
Related
Hi i have a flex file upload application over https it works fine on all IE browsers.
Recently a client with IE9 reported a complaint that she's not able to upload files.
I can see the error generated is IO Error #2038.
The adobe documentation says 2038 is File I/O Error.This error occurs when an application can't get file size, creation date or modification data using the FileReference API.
Can some one help me point out what could be the issue here.
All i can think of is browser issues like, browser cache, some new configuration in IE9 am unaware of or permission on the client directory.
Help will be much appreciated.
thanks
I suggest you to use Charles debugging proxy, which is must have tool for all Flash/Flex developers, and see the difference in IE8 and IE9. Maybe the problem is in some HTTP headers or something else.
I have a similar issue. Later I found out that upload feature doesn't work for latest version of flash player over https. Then I tried sending the upload requests via http instead of https. Now its working fine. Try this, it may help in your case aswell.
Hi I'm trying a simple tutorial of retrieving RSS feeds from yahoo and keep getting this error:
RPC Fault faultString="Security error accessing url" faultCode="Channel.Security.Error" faultDetail="Destination: DefaultHTTP"
I've seen some articles that say I need a crossdomain.xml file, but I don't really know how to set this file up and how to use it from the Flex SDK compiler (mxmlc).
Thanks
The crossdomain.xml file needs to live at the root of the server that you are accessing. If they have not put that there, then you are out of luck when running in the browser. It is part of an important security aspect of running in a browser sandbox (Silverlight has the same restriction). It is waived if you are running in Air (or pretty much anything out of the browser).
Lets say that you are trying to receive data from http://foo.com/rest/rss/all (or something like that). You can chec quickly to see if they allow cross-site scripting (XSC) by browsing to http://foo.com/crossdomain.xml. If it is not there, then you can't do it.
Still, the comments you got about more information would help us give you a better answer.
I have a browser compatibilty problem with https? I have SSL installed and is in usage. Until today morning, my https part is working well. From then, Https is shown as https(with slashed in red color) saying the page has some insecure content.
I have not changed any code and suddenly i see this problem in chrome. In IE 8, i see the same problem but on every page, it shows me a popup if i should allow to opne secure and non secure or just secure. Firefox has no issues . It shows correct https without any problem. I am fed up with it searching all over. Why is this happenening for me in Chrome and IE 8.
Could someone tell me what the problem is and what can be done to solve it!
PS: I have also checked if the page source is any different when IE8 showed with and without secure data. Everything is the same. but viewstateID was different. Is that something that is creating this problem?
Thanks a lot in advance.
This is usually caused by having the absolute path to a resource specified somewhere on the page without having https specified, eg:
<img src="http://someurl.com/image.png">
If it's a link to something on your site, use https: or a relative path.
DO you have any 3:rd party javascript included, like google analytics or other that might have changed.
If you try with Firefox there is firebug you can add as an addon.
In there is a tab for network (net).
It lists everything the page loads.
In that list you should be able to find anything that gets loaded without https.
IE (correctly) complains when there is mixed http/https content as a security warning. Most other browsers do not typically complain when dealing with mixed content so your source is very likely the same in both instances.
I would second David Mårtensson's answer and say the issue is likely a third party library (google or MS hosted JQuery for example) or static asset server.
i am using silverlight plugin 3.0 to display the chart.it is working fine on local pc but it is not working on server,it is not displaying any thing.
i have checked the MIME type also in iis.its over there.
please tell me whats the problem
thanking you
samir
Just to rule out the chart component itself, have you tried doing a simple "hello world" type application to see if it works?
This should test to see if it is the chart component/data source for it, or a general problem with your server/host and Silverlight.
It being a server, is IE in Extra Security Mode? It might not load up silverlight at all.
Do any silverlight things work? (I usually test with the gallery at silverlight.net).
I faced same problem. I used a perpetuum repoting tool. I had to create reporting services and these services are accessed by reporting viewer from client side. I forgot to change reporting services url. I put "localhost" and everything was blank(I saw blank page when access report).
so check if there is any issue like this...
or check this url about "URL Access Restrictions in Silverlight"
http://msdn.microsoft.com/en-us/library/cc189008(v=vs.95).aspx
I've been trying to work out why our pages load slowly, and one thing I've noticed in Fiddler is that each page load for /mysite/mypage.aspx brings with it a request for GET /mysite/null HTTP/1.1, resulting in a 404 error.
I'm guessing this 404 error on every page load is slowing the site down even further, are there any ways of debugging what might be causing this? We use lots of Ajax/Javascript.
Similar question: What is the source of /path/(null) requests?, ours is slightly different because it reliably happens on every page load
Get FireFox and download FireBug as you can use this to debug XHR.
Without seeing your code this is the best advice I can give you as tracking down these bugs are usually tedious and require some intimate knowledge of the working domain. FireBug is your best bet for debugging these sorts of issues within a page.
UPDATE:
Debugging the XmlHttpRequest object in IE can be done using Julien Couvreur's bookmarklet.
If you're using IE8, you can simply use the developer toolbar (hit F12) to step through your code.
The most likely explanation is that you have a malformed URL constructed by JavaScript somewhere in your page.