I'm trying to enable HTTPS support in my app before the October deadline, but the JavaScript call FB.getLoginStatus never calls my callback.
I'm using OAuth2.0, and I added the channelUrl parameter.
This works fine in HTTP mode.
FireFox is reporting no security warnings during page load, all files appear to be correctly served via HTTPS, and all references in the html/js code appear to be updated to point to https:// instead of http:// (including the channelUrl file).
What else can cause the getLoginStatus to not return?
Related
I use apache on my localhost for hosting sites that I'm working on.
I've started using firefox.
When I'm working locally on a website I don't set up SSL.
When I try to load my local site in firefox, firefox attempts to load the site with a 'https' prefix. This happens if I omit the protocal part of the URI, or if I explicitly type in 'http'.
Of course my site doesn't load. SSL is not enabled on the site.
How can I stop firefox from trying to redirect?
btw - the site itself consists of a single text file with the word 'hello' in that file.
There is no js or serverside logic implementing the redirect.
I have developed cloud application in ASP.NET. After every deployment, the portal either shows white screen or shows older version of the application.
Any suggestions would be highly appreciated.
I have already tried:
1) Updating JS version in each deployment (white screen issue was resolved by this)
2) Recycling Application Pool
3) IIS manager->http response header->set common headers->enable web content
4) Restarting IIS(8.5) after each deployment
However, none of these have worked. The application works fine in incognito mode of Chrome browser but not the regular one.
However, none of these have worked. The application works fine in incognito mode of Chrome browser but not the regular one.
As far as I know, if your brower has accessed your web application once, it will store the cache in client side.
If you modify the content and add the response header, it will not re-send the request to the server, it will use the cache page.
To aovid this, the only way is clear the browser's cache or use Ctrl+F5 to refresh the page.
Then if your reponse haeder contains the no-cache next time, the browser will not store the cache again.
I am using Eclipse 3.7.2 for PHP web app development.
When using the debugger (which I have setup to launch the application in Firefox), AJAX calls that are fired quickly contain a blank response when inspected with Firebug. This is not a cross-domain problem as the AJAX calls are all to the same server.
If I use Firebug to set a breakpoint just before the AJAX call in the JavaScript code, and then resume the execution, then the AJAX response will be loaded correctly.
It seems this problem may be due to Eclipse not being able to handle simultaneous requests. Is there any way to change Eclipse's settings to allow more requests?
Issue was due to using Zend Debugger. Switching to XDebug solved the issue. Also posted here - Using Eclipse PDT for debugging Ajax pages with concurrent requests
I'm trying to figure out right configuration for cross origin AJAX call in Safari extension injected script.
My configuration in Extension Builder:
Extension Website Access: All
Include Secure Pages: true
Whitelist: -
Blacklist: -
My goal is to get something like Chromes "permissions": "http://mysite.com/*", and be able to pull user configuration from web service.
note: JSONP drops warning, so I would prefer to avoid it.
Any luck with this? I'm having the same problems. Same setup works fine in the Chrome extension, but hitting Access-Contol-Allow-Origin when trying to do it in Safari Extension.
FIXED - UPDATE:
Hey, I figured out what the problem is. So, it looks like you need to do the cross-domain ajax via the background page. What I end up doing is determining all the requests I need to make in the injected script, then message pass the requests to the background page. The background page listens for messages from the injected script, makes the appropriate ajax calls, and then sends the results via a message to the injected script. The injected script is then listening for messages from the background page, once it gets the message(s) with the ajax results, it takes the appropriate action in the page that's being viewed.
I have a page that gathers environment status from a couple of IBM WebSphere servers using iframes similar to this:
<iframe src="http://server:9060/ibm/console/status?text=true&type=server&node=NODE&name=ServerName_server_NODE"></iframe>
and it happily prints out "Started" or "Unavailable" etc. But if I load the same url in a normal browser sometimes it works, sometimes it does not? Some of them are showing a login page, while others are simply return HTTP code 500.
So whats the difference between loading the page through an iframe vs through a browser?
I can tell you that the iframe solution works no matter which machine I am doing it on, so I do not belive it has anything to do with the user whos opening the page. And before you ask, why not keep the solution that works, well its because it takes a long time to open the page with the iframes vs a page where everything is requested through ajax.
Update: Using jQuery to perform the ajax call returns "error" and "undefined" for the servers that I can't see in a normal browser.
One difference is an iframe has to render the view while XHR would not.
An iframe is essentially the same as opening with the browser. In both cases the browsers credentials are used, so there will be no difference between the two.
Secondly, loading something in an iframe should take the same amount of time as requesting it through XHR, since in both cases the browser makes an HTTP request and waits for the response. Although I should add that an iframe will take time to render the content onto the page. However if you plan on displaying it with ajax anyways, an iframe/xhr solution will be more or less the same.
In case of ajax request same origin policy (which restricts cross domain call) comes into picture. So you can't make cross domain call using xhr. Alternative for same is embed flex swf file in your page as activex control and make flex call through javascript and then flex is responsible to make cross domain call (flex can if targeted domain allows cross domain using crossdomain.xml) and renders result using javascript again.