If I display my website with HTTP everything is fine. But when I browse with HTTPS, Skype button is not rendered.
Chrome shows this error on console:
Failed to load resource: net::ERR_INSECURE_RESPONSE
https://www.skypeassets.com/i/scom/js/skype-uri.js
And my code is:
<script type="text/javascript" src="//www.skypeassets.com/i/scom/js/skype-uri.js"></script>
<div id="SkypeButton_Call_gamirasu.cave.hotel_1" style="float: right; width:85px !important; height:23px !important; margin-top:-65px;">
<script type="text/javascript">
Skype.ui({
"name": " ",
"element": "SkypeButton_Call_gamirasu.cave.hotel_1",
"participants": ["gamirasu.cave.hotel"],
"imageSize": 24
});
</script>
I couldn't find anything about using Skype with SSL on their document. Any help will be appreciated.
You need to use this specific secured (HTTPS) domain for Skype widgets:
https://secure.skypeassets.com/i/scom/js/skype-uri.js
Have you tried visiting the URL you provided ? When I try using Chrome, I get to an SSL warning, which is the explanation why you can't load this ressource.
Related
I tried to use Google Sign-in for my website, however, it keeps giving me 400 error.
I referenced this article: https://developers.google.com/identity/sign-in/web/sign-in, and my code is really simple:
<html>
<head>
<title>Test Google Login</title>
<script src="https://apis.google.com/js/platform.js" async defer></script>
<meta name="google-signin-client_id" content="<CHANGE IT>">
<script>
function onSignIn(googleUser) {
var profile = googleUser.getBasicProfile();
console.log('ID: ' + profile.getId());
console.log('Name: ' + profile.getName());
console.log('Image URL: ' + profile.getImageUrl());
console.log('Email: ' + profile.getEmail());
}
</script>
</head>
<body>
<div class="g-signin2" data-onsuccess="onSignIn"></div>
</body>
</html>
When I click Sign-in button, it popups a window, and after logged in, it gave me 400 error as below:
400. That’s an error.
The requested URL was not found on this server. That’s all we know.
I guess it's redirect issue, but I don't know how to configure it. So I checked url it returned to me:
https://accounts.google.com/o/oauth2/auth?fetch_basic_profile=true&scope=email+profile+openid&response_type=permission&e=3100087&redirect_uri=storagerelay://http/127.0.0.1:8000?id%3Dauth867179&ss_domain=http://127.0.0.1:8000&client_id=378468243311-9dt7m9ufa9mee305j1b12815put5betb.apps.googleusercontent.com&openid.realm&hl=en&from_login=1&as=1b5f0a407ea58e11&pli=1&authuser=0
Why is redirect_uri "storagerelay://http/127.0.0.1:8000?id%3Dauth867179"?
Your code should work now.
Google fixed this issue. Origins with a trailing slash are also accepted now (Origin can be set in Google Developers Console > APIs & auth > Credentials).
Redirect URIs
http://localhost:8000/ this **/** at end solve my problem
JavaScript origins
http://localhost:8000
NOTE: localhost and 127.0.0.1 conflicts can create problems for you sometime
Hi I faced exactly same problem.
Regarding my case, the problem is that OAuth try to redirect to url of "127.0.0.1?id=authxxxxx" where xxxxx is random 5 digits.
Thus I added following four urls at Redirect URI Google Developers Console.
I am not sure which one hits the rule, but I could workaround with this
(1) http://127.0.0.1/*
(2) https of (1)
(3) http://127.0.0.1
(4) https of (3)
Hope it also works for you.
To test on localhost environment, here's things we should to do:
Add "http://localhost:8000" to "JavaScript origins"
Remove everything from "Redirect URIs", because JavaScript API doesn't need any redirect URIs
[1] https://developers.google.com/identity/sign-in/web/devconsole-project
I'm also having the same problem, and was able to get past it by using "localhost" instead of the ip address. It's not a great solution, but it was sufficient for me to continue debugging in dev, so I just thought I'd mention it.
edit: keep in mind that you will have to add http://localhost to your Google Oauth Javascript Origins.
I had the same problem yesterday. I had OAuth credentials with localhost and my-server.com. So, I fixed this problem creating a new OAuth credentials only for my-server.com, without localhost. Obviusly, my app uses these new credentials.
I found out that error disappears after clearing ACCOUNT_CHOOSER accounts.google.com cookie.
Replace everywherehttp://127.0.0.1:8000/ to HTTP://localhost:8000/even in your browser too. The Problem comes when you use http://127.0.0.1:8000/ either in the developer console or a browser.
i'm working on upload site in c# i'm currently using uploadify flash Uploader with ASP.NET
when i upload my file The session information in firefox is empty but in other browser chrome opera safari ie working fine uploadify send post request which cause problem in session
Any Solution for this problem ?
i solved this problem by using little technique
i have add encrypted username at the end of upload when request send to upload page the upload page will decrypt username if it's not successful then don't perform upload
<script type="text/javascript">
$(function() {
$('#file_upload').uploadify({
'formData' : {
},
'fileSizeLimit': '20000KB',
'buttonClass': 'mybtn',
'swf' : '../assets/uploadify.swf',
'uploader': 'upload.aspx?u={i add encrypted username here}',
'uploadLimit' : 20
});
});
</script>
Using this code on the client side:
<script src="//ajax.googleapis.com/ajax/libs/jquery/1.6.2/jquery.js"></script>
<script src="http://cdn.socket.io/stable/socket.io.js"></script>
<script type="text/javascript">
$(document).ready(function () {
var socket = io.connect('http://localhost:8888');
});
</script>
Getting this error:
"io.connect is not a function"
Any suggestions?
The answer was I had to use my external ip address for the server this script is running on.
The biggest problem is that http://cdn.socket.io/stable/socket.io.js is code for Socket.IO 0.6 and you are using the Socket.IO 0.7+ API.
The CDN has been deprecated and should no longer be used. Here is a wiki about how to serve the socket.io client in your HTML pages: https://github.com/LearnBoost/Socket.IO/wiki/How-do-I-serve-the-client
I'm trying to integrate google checkout with a magento site and get the following error in the Integration Console:
We encountered an error trying to access your server at
https://www.domain.co.uk/googlecheckout/api/
-- the error we got is Sending failed with HTTP response
code: 404. Response body was: <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"> <head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1"/>
<title>404 - File or directory not found.</title> <style type="text/css">
<!-- body{margin:0;font-size:.7em;font-family:Verdana, Arial, Helvetica, sans-serif;background:#EEEEEE;}
fieldset{padding:0 15px 10px 15px;} h1{font-size:2.4em;margin:0;color:#FFF;}
h2{font-size:1.7em;margin:0;color:#CC0000;}
h3{font-size:1.2em;margin:10px 0 0 0;color:#000000;}
#header{width:96%;margin:0 0 0 0;padding:6px 2% 6px 2%;font-family:"trebuchet MS", Verdana, sans-serif;color:#FFF; background-color:#555555;}
#content{margin:0 0 0 2%;position:relative;}
.content-container{background:#FFF;width:96%;margin-top:8px;padding:10px;position:relative;} -->
</style> </head> <body>
<div id="header"><h1>Server Error</h1></div>
<div id="content"> <div class="content-container"><fieldset> <h2>404 - File or directory not found.</h2>
<h3>The resource you are looking for might have been removed, had its name changed, or is temporarily unavailable.</h3>
</fieldset></div> </div> </body> </html>
As far as I can tell, it's not actually a 404 error as I can do the following:
wget --post-data=blah https://www.domain.co.uk/googlecheckout/api/
--10:58:43-- https://www.domain.co.uk/googlecheckout/api/
=> `index.html'
Resolving www.domain.co.uk... 192.168.1.117
Connecting to www.domain.co.uk|192.168.1.117|:443... connected.
HTTP request sent, awaiting response... 503 Service Unavailable
10:58:43 ERROR 503: Service Unavailable.
Now the 503 error there actually relates to me not sending any HTTP_AUTHORIZATION with wget, so it dies on this line strpos($_SERVER['HTTP_AUTHORIZATION'], " ") + 1))); in googleresponse.php. This isn't the problem.
I have tried both https://www.domain.co.uk/googlecheckout/api/ and https://www.domain.co.uk/googlecheckout/api in both wget and Google Checkout settings callback URL with the same results.
I've made sure that always_populate_raw_post_data = On is set, and it's showing up correctly in phpinfo().
I've tried debug mode On and Off in Google API settings within Magento.
The checkout process was working correctly on a dev domain using the sandbox mode.
I've tried all of the things that I could find with google searches. Any other options would be greatly appreciated.
Edit
It looks like that response is from an IIS server. The server that this site is now running on is Apache. Could Google still be accessing the old server? DNS was updated over 15 hours ago.
Check the server logs on the old and new servers to see which one Google made the request to.
That original error from google is an IIS 404 page, not an apache 404 page, so it seems as though google is looking at a different web server.
I am using jquery tabs to load content from a remote file. I have about 30 links in tabbed navigation all loaded with the same script, but for some reason I get 404 errors on 3 or 4 of the links. Each time I reload the page, the links that don't work will change, so some links that didn't work previously will load properly and others that worked before will throw a 404. The load function happens to create a jcarousel but fire but shows that it gets a 404 error.
$('#example > ul').tabs({
fx: { height: 'toggle', opacity: 'toggle'},
load: function(event, ui) {
$(ui.panel).find('.jcarousel-skin-tango').jcarousel({scroll: 5, easing:'easeInOutQuad', animation:800});
$(ui.panel).find('.jcarousel-skin-tango ul').css({"width":'2890px', "left":"0pt"});
}
});
//----------------------------------------------
<ul>
<li><span>A</span></li>
<li><span>B</span></li>
<li><span>C</span></li>
...
</ul>
Any help would be greatly appreciated. Thanks in advance.
My guess (with very little information) is that it has nothing to do with jQuery or AJAX, but some kind of threading problem either in PHP or in the web-server itself. If you open the same URLs as iframes, do they work then?