New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 801085 link

Starred by 2 users

Issue metadata

Status: WontFix
Owner: ----
Closed: Jan 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug



Sign in to add a comment

Access-Control-Allow-Origin error on the same site

Reported by durancan...@gmail.com, Jan 11 2018

Issue description

UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/63.0.3239.132 Safari/537.36

Steps to reproduce the problem:
1. wtf is this ?
2. The code I wrote works fine with mozilla. Chrome also has an error

3. Simple using $.get or $.post
4. And i have on php file header('Access-Control-Allow-Origin: *');  but chrome still not work.

What is the expected behavior?
1. wtf is this ?
2. The code I wrote works fine with mozilla. Chrome also has an error

3. Simple using $.get or $.post
4. And i have on php file header('Access-Control-Allow-Origin: *');  but chrome still not work.

What went wrong?
1. wtf is this ?
2. The code I wrote works fine with mozilla. Chrome also has an error

3. Simple using $.get or $.post
4. And i have on php file header('Access-Control-Allow-Origin: *');  but chrome still not work.

Did this work before? N/A 

Chrome version: 63.0.3239.132  Channel: stable
OS Version: 10.0
Flash Version:
 
Adsız.png
372 KB View Download

Comment 1 by vivekh...@gmail.com, Jan 11 2018

same with MacOs High Sierra

Comment 2 by tkent@chromium.org, Jan 11 2018

Components: -Blink Blink>SecurityFeature
Labels: Needs-Triage-M63
Cc: sc00335...@techmahindra.com
Labels: Needs-Feedback Triaged-ET
Unable to reproduce this issue on reported version 63.0.3239.132 using Windows 10, Ubuntu 14.04,Mac 10.13.1 with steps mentioned in comment#0. i.e; "No Access-Control-Allow-Origin is present" message is not seen in console of devtools. Attaching screencast for reference.

@Reporter: Could you please check the video and let us know if we miss anything. This would help in further triaging of the issue.

Thanks!



Attaching screencast for reference.
801085.mp4
5.0 MB View Download

Comment 6 by mkwst@chromium.org, Jan 16 2018

Hi, durancangames@. There's not much information in the bug report, but from the console logs you pasted, it looks like you're requesting `https://oyunkodla.com/` from `https://www.oyunkodla.com/`. Those are distinct origins, and would require the former to opt-into the request by sending appropriate CORS headers.

I can't reproduce the error when loading the page myself. Have you fixed it on the server-side?

Comment 7 by mkwst@chromium.org, Jan 16 2018

Cc: mkwst@chromium.org
Components: -Blink>SecurityFeature Blink>SecurityFeature>CORS

Comment 8 by mkwst@chromium.org, Jan 22 2018

Status: WontFix (was: Unconfirmed)
Closing this out due to inability to reproduce. If there's a reproduction case I should take a look at, please do ping this bug or open a new one. :)

Sign in to add a comment