cross-site

CORS policy with Google Storage allows from my origin, but no 'Access-Control-Allow-Origin' header is present

橙三吉。 提交于 2020-08-10 20:02:31
问题 I'm new to CORS configuration and trying to figure this out, but my set up looks like it is right according to the documentation. I'm hoping you can help me see what I've missed. My code is trying to upload ( PUT ) a file directly to google storage using a signed url. Access to XMLHttpRequest at 'https://storage.googleapis.com/herdboss-dev.appspot.com/uploads/152/152-owner-152-61.jpg?X-Goog-Algorithm=GOOG4-RSA-SHA256&X-Go...' from origin 'https://herdboss-dev.appspot.com' has been blocked by

Confusion regarding SameSite changes with Chrome

徘徊边缘 提交于 2020-08-04 07:55:44
问题 I need some help understanding a case which I can not find described in material I have found describing the new SameSite restrictions for Chrome. Currently, I have a case where I have a site hosted which makes cross-site requests to an API. The API responds with CORS headers. The details are: Site: https://a.a.com API: https://b.a.com --API response headers Access-Control-Allow-Credentials: true Access-Control-Allow-Origin: https://a.a.com --cookie previously set with Set-Cookie: value

Error: AADSTS50058: A silent sign-in request was sent but no user is signed in - Angular ADAL authentication issue in mobile safari browser

允我心安 提交于 2020-07-21 07:01:39
问题 We have a site developed using Angular 7 and it uses Adal-Angular4 library for Azure Active Directoty authentication. When the site is browsed in safari on iPhone, it runs into below error. Error: AADSTS50058: A silent sign-in request was sent but no user is signed in. The cookies used to represent the user's session were not sent in the request to Azure AD. This can happen if the user is using Internet Explorer or Edge, and the web app sending the silent sign-in request is in different IE

Error: AADSTS50058: A silent sign-in request was sent but no user is signed in - Angular ADAL authentication issue in mobile safari browser

徘徊边缘 提交于 2020-07-21 07:01:11
问题 We have a site developed using Angular 7 and it uses Adal-Angular4 library for Azure Active Directoty authentication. When the site is browsed in safari on iPhone, it runs into below error. Error: AADSTS50058: A silent sign-in request was sent but no user is signed in. The cookies used to represent the user's session were not sent in the request to Azure AD. This can happen if the user is using Internet Explorer or Edge, and the web app sending the silent sign-in request is in different IE

google maps - Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at

蹲街弑〆低调 提交于 2020-06-25 21:37:07
问题 I am using google maps api and on the page I have this <link type="text/css" rel="stylesheet" href="https://fonts.googleapis.com/css?family=Roboto:300,400,500"> now, because of this, as you can see in this link https://fonts.googleapis.com/css?family=Roboto:300,400,500 there are font files - included by url, and AFA i understand it causes the problem. In firebug it shows Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://themes

jquery solutions to post to another site from static html page

ぃ、小莉子 提交于 2020-01-13 11:05:30
问题 Need to post data from a static html page to another page which is hosted on another domain. Normally I'd create and iframe with a form inside of it with a post method, and whose actions is directed to that web page, and finally submit that form. The complexity is I'd collect data from my static html page and create a similar (replica) form inside the iframe (with the above attributes viz method & action mainly); if there are a lot of fields I'd struggle to do it via javascript alone. So are

Why is cross-domain JSONP safe, but cross-domainJSON not?

流过昼夜 提交于 2020-01-11 15:48:52
问题 I'm having trouble connecting some dots having recently learned of JSONP. Here's my understanding: Cross-domain XmlHttpRequests for any content (including JSON) is banned, due to the same origin policy. This protects against XSRF. You are permitted to have a script tag with a src that returns JSONP - some JSON padded inside a call to a Javascript function (say 'Foo') You can have some implementation of 'foo' on the page that will get called when the JSONP data is returned, and you can do

Why is cross-domain JSONP safe, but cross-domainJSON not?

前提是你 提交于 2020-01-11 15:48:29
问题 I'm having trouble connecting some dots having recently learned of JSONP. Here's my understanding: Cross-domain XmlHttpRequests for any content (including JSON) is banned, due to the same origin policy. This protects against XSRF. You are permitted to have a script tag with a src that returns JSONP - some JSON padded inside a call to a Javascript function (say 'Foo') You can have some implementation of 'foo' on the page that will get called when the JSONP data is returned, and you can do