I am making a GET request for the connect sdk script: https://connect.soundcloud.com/sdk/sdk-3.1.2.js, which has never before failed me before. This file is the one the documentation says to use. However when I make a GET request to: https://connect.soundcloud.com/sdk/sdk-3.1.2.js in a script tag, postman, and in my browser url bar, the return status is 404 Not Found.
Please help me, as my application artistsunlimited.co uses the connect api heavily.
It looks like they deployed some code today; this may be related, because I was not getting this error yesterday. Hopefully they will fix this issue soon.
See status message here.
Related
I'm trying to upload files with Service worker BackgroundFetch api(with Chrome 102.0.5005.61) and aws-sdk library(version 2.828.0).
First, I had to patch aws-sdk to work with browser fetch apias described here, and it worked well.Then when I replaced window.fetch with SW background fetch it fails with "backgroundfetchfail" event(BackgroundFetchUpdateUIEvent) showing that BackgroundFetchUpdateUIEvent.registration.failureReason is "fetch-error". no info besides that...please if anyone knows how to get more info? might be some request header generated by aws-sdk that fails the request?
EDIT: Adding a codeSandBox for debugging: sandbox
First time posting here so don't hesitate if you need/I forgot something. I looked everywhere and didn't find my answer (I guess I'm missing something).
My problem:
I created a REST SpringBoot application and put an index.html in resources/static to create a REACT front end (I don't want to use nodejs, maybe webpack if I really have to).
When I contact localhost:8080/ I end up on my index.html but those scripts:
<script src="https://facebook.com/react-15.2.0.js"></script>
<script src="https://facebook.com/react-dom-15.2.0.js"></script>
needed to make REACT work provoke a Proxy Authentication Required error in the console log.
I am indeed behind my company's proxy. My IDE (IntelliJ) is configured with this proxy. My JVM takes those arguments to make it work:
-Dhttp.proxyHost=myproxy -Dhttp.proxyPort=myport -Dhttp.proxyUser=myuser -Dhttp.proxyPassword=mypwd -Dhttp.proxySet=true
and the application.properties has the following line:
server.use-forwarded-headers=true
I don't know what I should configure anymore to make it work. Do you have any ideas? Thank you very much in advance!
EDIT:
Facebook is a bad example as the proxy won't let me go on this site. I have updated my src to authorized sites (tried them on my browser and they worked). Still, I have the same error: 407 Proxy Authentification Required
I found the solution:
The error is legit. This is the HTTP protocol. First I have the 407 error asking for the informations of my proxy, then those informations are sent throught a second request. Still, showing an error in the log is disturbing.
My web-app has the Facebook JS SDK implemented.
Yesterday, everything was working fine and without any modification on the code, the script request started to return 404 errors.
When I try to access it directly, this is what I find:
Facebook Status shows that the API everything is OK.
Instagram's embeds.js and Facebook's debug SDK are also returning the same error:
Does anyone knows what it happening? I've tried accessing these files using my 4G network and the same error is displayed.
I'm based in Dublin, Ireland.
I figured this one out.. it seems the .net isn't working anymore.. I used ".com" instead:
Use https://connect.facebook.com/en_US/sdk.js
instead of https://connect.facebook.net/en_US/sdk.js
It is related to this bug, subscribe to get updated: https://developers.facebook.com/bugs/949091578557056/
There is a workaround to use .com instead of .net.
Edit: The bug is fixed now.
I had the same problem. Use //connect.facebook.com/en_US/sdk.js url.
I'd like to use Google Execution Api from my chrome extension.
On the page below, there is a form to test execution api request, but when I send request, I get 403 error as response.
This person who posted this question seems to have solved his problem which is probably the same problem as mine.
Why does my apps script deployed as API executable return Permission Denied?
But, I can't solve this error. Please guide me to help me this error.
Request
This is what I input into request form.
https://developers.google.com/apps-script/execution/rest/v1/scripts/run#try-it
Response
{
"error": {
"code": 403,
"message": "The caller does not have permission",
"status": "PERMISSION_DENIED"
}
}
Project Key : MVO00WF1oNYdJ7YvOZGxXh_z7UcVTY4Um
Scopes
I use spread sheet api so, I added spread sheet scope as additional scope for OAuth 2.0.
code.gs
This is a sample function code to call.
// This function does nothing. Just a test.
function myFunction(data) {
var sheet = SpreadsheetApp.getActiveSheet();
return "success!!";
}
The script associated with project
Additional Info
I deployed my project as API executable.
I enabled execution API on developer console.
I made OAuth 2.0 Client ID on developer console.
Reference
https://developers.google.com/apps-script/guides/rest/api#limitations
is the script public or for your use only? I got this error and it resolved when I made the script public. I was doing an Android app so the answer may not apply completely.
I was having similar problems running through the quickstart documentation provided by Google. I noticed you have two items in your scope. Be careful that you add the second scope to your array. For me, I was using the node.js quickstart so line 10 looked like this:
var SCOPES = ['https://www.googleapis.com/auth/drive', 'https://www.googleapis.com/auth/spreadsheets'];
Also, as the line above this one (lines 8-9) indicates, I had to rm my previous credentials. Go to your home directory and find (the hidden) folder .credentials. for me the command was:
me#mydrive:~/.credentials $ rm script-nodejs-quickstart.json
One I did this, I re-ran my script, got authorized, and had it all working.
Your 403 error indicates that you have incorrectly or missed some configuration in authentication for your service account. Make sure the app script is associated with correct dev console project.
The script should be associated with the dev console project id that corresponds with OAuth 2.0 client ID used (this dev console project should also have "Apps Script Execution API" enabled).
To change the developer console project for an app script select the following menu item: Resources > Developer Console Project.
I had the same problem yesterday: I got the same error although I did everything correct.
I solved it by having deleted the .credentials file und rerun the code. Try it out if didn't do that before.
I'm using App Engine's Channel API to maintain a connection between a Chrome extension and an App Engine app. You can see my Channel-related code here: https://github.com/2cloud/Chrome/blob/3fe70262ef69ae8286a057055f4108760560c47e/socket.js (The app is open source, so you can check out the repository to get an idea of how it all fits together)
My issue is, for some reason, the 401 error that App Engine throws when a token expires isn't being sent to my onError listener. I've tried just logging the error object from within onError, outside of an if statement, and still got nothing. My conclusion was that onError isn't getting called when a 401 is thrown, as the documentation says it's supposed to.
Has anyone else seen this error? Does anyone else have an idea on how to fix it?
I've reproduced this bug and started work fixing it. http://code.google.com/p/googleappengine/issues/detail?id=5685