Issue with Chrome calling cross domain jsonp resource via jQuery ajax -


solved - adblock plus

i have cross-domain oauth scenario i'm calling oauth protected jsonp resources on 3rd party api directly javascript.

the client relies on server (the site of origin) generate signed request urls oauth resources on provider. client gets these oauth resources directly in attempt limit oauth proxy duties of server generating signed resource urls , letting js rest. here's js:

mynamespace = {     callapi: function(signedrequest, callback) {         $.ajax({             url: signedrequest,             datatype: "jsonp",             type: "get",             crossdomain: true,             jsonp: false,             jsonpcallback: callback,             cache: true,             async: true         });     },     userscallback: function(jsonp) {         alert(jsonp);     },     getoauthresource: function(resource, callback) {         $.ajax({             url: "/getsignedrequest?resource=" +  encodeuricomponent(resource + "&callback=" + callback),             success: function (signedrequest) {                 mynamespace.callapi(signedrequest, callback);             }         });     } }

because parameter order matters when signing request, include callback manually gets ordered & included in signed request server generates.

so example usage simply,

mynamespace.getoauthresource("/users?id=1", "mynamespace.userscallback");

this working in firefox 20 , ie 10 - alert msg & expected json provider.

chrome 26 refuses perform cross-domain call provider. in dev tools, cross-domain resource shows status of "(failed)" , shows in console error.

if subsequently ask chrome open supposedly "failed" url in new window, re-requests url directly on provider , expected jsonp response:

mynamespace.userscallback({...})

why won't chrome perform cross-domain call?


Comments

Post a Comment

Popular posts from this blog

Why does Ruby on Rails generate add a blank line to the end of a file? -

running rails generate controller foo home results in: class foocontroller < application controller def home end end (there's nothing on line in actual file, blank line) is there purpose blank line? it's common use newline indicate end of line, last line. many editors (like vi, use) add in newline silently. consensus text files (especially in unix world) should end in newline, , there have been problems historically if wasn't present. why should text files end newline? the tool used count lines in file "wc" counts newlines in file, without trailing newline show 3 instead of 4. it improves readability of templates used in generator. consider: https://github.com/rails/rails/blob/master/railties/lib/rails/generators/rails/controller/templates/controller.rb to remove trailing newline, template have last line of: end<% end -%> instead of: end <% end -%> that seems less readable me. the discussion below refers ...
Read more

keyboard - Smiles and long press feature in Android -

i've created android keyboard. how add features inserting smilies, , using long keypresses display symbols? to create long-press behavior allows select several options pop-up menu, follow guide (specifically pop-up menu section): http://developer.android.com/guide/topics/ui/menus.html smileys (also known emoticons) combination of keys, understood programs , parsed same way. have do, when clicks smiley face on keyboard, simulate pressing of key combination matching emoticon. example, when clicks smiley, should simulate key presses ':' , ')' :). here's list of emoticons: http://en.wikipedia.org/wiki/list_of_emoticons
Read more

node.js - Bad Request - node js ajax post -

i'm using express 3.0 , node v0.11.0. have button submits form , i'm using ajax post data json object node server. client code is: $('#contact').submit(function(e) { console.log('submit called'); var formdata = json.stringify($('form').serializeobject()); console.log(formdata); $.ajax({ url: "http://localhost:3000/savedata/", type: "post", datatype: 'json', data: {objectdata: formdata}, contenttype: "application/json", complete: function() { console.log('process complete'); }, success: function(data) { console.log('process sucess'); }, error: function() { console.log('process error'); }, }); return false; }); then on server: var express = require('express'); var app = express(); app.set('views', __dirname + '/views'); app.set('view engine', 'jade'); app.use(express.bodyparser());...
Read more