Windows Live JS file - error 400 - windows-live

I just try to add Windows Live Connect JS API to my project and have an error:
GET http://js.live.net/v5.0/wl.js 400 (Bad Request)
This is the way I try to get it:
<script src="http://js.live.net/v5.0/wl.js" type="text/javascript"></script>
Any ideas ?

By Microsoft:
This is a known issue and we're looking into it. We apologize for the inconvenience.
Source (You asked the question there so you probably know it, but I am posting the answer here to help other users with the same problem)

Related

I have a problem with my NODEJS API on planetHoster

I created my very first NODEJS API. Locally, it works well but I just hosted it on planetHoster and it doesn’t work anymore. When I enter my query, I find the error "Cannot GET/Nodev2/idcc/list" then my route was functional locally. Do you have any assumptions? Thank you in advance!
I can share my code if you want see
I tried to change directory/file names

ERR_CONNECTION_REFUSED and Failed to fetch (nodejs, graphql, apollo)

I am newbie on JS frameworks, so sorry if my question is easy but I didn't find any solution on my Google friend :)
I am creating a web app with ReactJS in Front-End, NodeJS in Back-End, GraphQL and Apollo.
I have my Back-End that works on localhost:4001/api (I am viewing the GraphQL interface with a query).
I have my Front-End that's working when I am not connected to my server. But when I am connected it, I have two errors (I think they are linked).
I have in my console :
Bug
I resolved the cors error but here, I am blocked. I tried bearer-authentication, but I'm not sure how can I use it and I'm not sure it's the a problem, but bearer solved this two bugs, but created the bug "Network error: Response not successful: Received status code 400" (is it permission?)
You can view my github repo here : https://github.com/tiffanyLestroubac/ReactJs-NodeJs-GraphQl-App
Thanks in advance :)

Linked in previews not working

I have searched all over the internet for an answer and although I can find a million people with the same question I cannot find an official solution to the problem im experiencing.
I always get "Cannot display preview. You can post as is, or try another link." displayed.
I've stripped a page down to only the required open graph meta tags so I know they work (run through multiple OG validators), Ive disabled any kind of robots blocking, any kind of redirects, disabled the firewall on a test server, made sure the LinkedIn bot requests are hitting the server. All I see in the browser console all the time is a status 500 being returned from LinkedIn's preview generator API.
We are hosting on Windows Server in IIS 8.5, it seems if I create a demo and host it somewhere else it works, which makes me think it is server related or IIS settings.
Reading this Linkedin post's picture doesn't appear in summary its seems like a similar issue. We are not serving over SSL so nothing to do with that.
I have already asked this question on LinkedIn's forum but having no luck, so im hoping someone on here can help or someone from LinkedIn's tech team can help.
Thanks
So we had this issue as well and it turns out parts of our system that use user generated themes were not adding the "Content-Type" header to the response.
So examine the response headers coming from your server and make absolutely sure they are correct and that they include the correct "Content-Type" (with correct encoding) and "Content-Length".

azure 502 bad gateway

has anyone seen this before so I am getting a 502 bad gateway error on my app, the issue I have is that the detailed error information I am getting says my requested url is https://SOX:80/api however my site is configured to use https://sox.domain.com and the site largely works pulling the various JS files required
my app service name is SOX in the azure dashboard so I assume that is where it is picking up SOX from but I have no idea why it is using this.
So overall the issue had me perplexed... however with more testing I soon figured out what was going on.
my backend is Dotnet core Azure throwing the 502 bad gateway was its way of handling exceptions ultimately the problem was code based.
I am mentioning this purely so that it will help others
my first issue was based on cert handling it seems dotnet runs in a container that is specified by your app name as i mentioned above https://SOX:80
the below was causing my issues
sslPolicyErrors = X509StoreStoreHelper.ValidateSSLPolicy(cert.Thumbprint, cert);
after commenting this out for testing my problem went away(we are putting in a proper fix )
my second issue came from using an unsupported view in Azure SQL master.sys.master_files which again just threw a 502 bad gateway error referencing https://SOX:80
please note I have used https://SOX:80 as a reference to mask the real site.
hope this helps the next person.
Based on your description, I have checked your site (https://sox.azurewebsites.net/) and found that it contains three static files (index.html,generic.html,elements.html). I viewed your website in Chrome incognito window as follows:
I did not find any requests against https://SOX:80/api in your html page or JavaScript files. Please try to access your website in a new incognito window to isolate the cache issue or just press CTRL + F5 to refresh your current page to narrow this issue. Moreover, you need to check whether you have configured URL Rewrite. If you still could not solve this issue, you need to update your question with the details for us to reproduce this issue.

403 error on Lighthouse3D's web

I am really pissed about the fact, that Lighthouse tutorial web (http://www.lighthouse3d.com/) is throwing me 403error forbidden. Don't you know what they are doing, or will it be in the future online? I helluva need it to my school.
It might be that they do something on their side , or if site requires some kind of auth , they didn't provided solution nor explanataion. Tried to load it , same happens. Might be that Apache server and mods has to be restarted or fixed. I got many times 403 error , like when I try to open www.openlicenser.org which also throws this error , and it wasn't fixed yet , I think.
As Rudolf said, the website is experiencing problems on server side.
But, if you want to check something urgently here is a useful link:
http://web.archive.org/web/20130216083928/http://www.lighthouse3d.com/

Resources