Issue metadata
Sign in to add a comment
|
No 'Access-Control-Allow-Origin' header is present on the requested resource. Origin 'https://mywebsite.com' is therefore not allowed access. Canary is good.
Reported by
dent...@gmail.com,
Nov 6 2017
|
||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/62.0.3202.75 Safari/537.36 Steps to reproduce the problem: 1. When I open website everything is good. 2. I open the Dev-Tools > tab "Application" > check "Bypass for network" > tab "Network" > check "Disable cache" 3. F5 (or Ctrl + R) and I got the error. 4. Ctrl + Shift + R and the problem disappear. What is the expected behavior? Everything good. What went wrong? I got: "No 'Access-Control-Allow-Origin' header is present on the requested resource. Origin 'https://mywebsite.com' is therefore not allowed access.". I think it is because when in "Disable cache" and in "Bypass for network" in the "Network" tab there isn't the "OPTIONS" method pre-flight call to the API. And the only one GET request is without "Origin" in the "Request headers". Problem in: Chrome STABLE (62), BETA (63). Everything good in: Chrome CANARY (64). Am I wrong somewhere? Did this work before? Yes 61 (I think) Chrome version: 62.0.3202.75 Channel: stable OS Version: 10.0 Flash Version: - My app is a new "create-react-app" with Sevice Worker, but the problem I think is not because of this, because it's also on "localhost" and with service worker disabled. I'll try another app.
,
Nov 6 2017
,
Nov 7 2017
Tested on reported Chrome version #62.0.3202.75, latest Stable #62.0.3202.89 and latest Canary #64.0.3260.0 on Windows 10 and unable to reproduce the issue mentioned. Please refer the screencast attached. Steps Followed: 1. Tried navigating to the site: 'https://mywebsite.com/', received an error 'This site can’t be reached'. 2. Therefore navigated to the site 'https://www.google.co.in/'. 3. Opened Dev tools and updated the settings: Application > checked "Bypass for network" & Network > check "Disable cache". 4. Refreshed screen by performing the keyboard action 'F5'. Observations: Able to load the screen without any errors. @Reporter-- Could you please try by removing the extensions and creating a new profile to verify if the issue still persists. You can also try by updating your Chrome to latest Stable version. Please let us know if we have missed anything. Thanks in advance. **Updated User Name mentioned in C#3 and reposting the same comment as per reporter's request.**
,
Dec 13 2017
If Canary works fine, closing it as fixed |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by ligim...@chromium.org
, Nov 6 2017