-
Notifications
You must be signed in to change notification settings - Fork 478
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
OutOfBlinkCors: M85 POST requests fail with net::ERR_FAILED #3006
Comments
Original comment by Salvador Diaz Fau (Bitbucket: salvadordf, GitHub: salvadordf). typo |
Original changes by Salvador Diaz Fau (Bitbucket: salvadordf, GitHub: salvadordf).
|
Thanks for creating this issue. |
|
Related forum thread: https://magpcss.org/ceforum/viewtopic.php?f=6&t=17826 |
|
Original comment by Salvador Diaz Fau (Bitbucket: salvadordf, GitHub: salvadordf). Added forum thread link |
Original changes by Salvador Diaz Fau (Bitbucket: salvadordf, GitHub: salvadordf).
|
Looking at the net log (created with chrome://net-export) for the Google QR request, with OutOfBlinkCors disabled:
And with OutOfBlinkCors enabled:
|
The
|
After
That results in a call to In other words, the “OPTIONS” request via |
With OutOfBlinkCors disabled the “OPTIONS” request that arrives in
With OutOfBlinkCors enabled the “OPTIONS” request arrives from
|
With memory addresses removed the diff between the two results is:
The most important one might be the missing |
Missing
|
|
Well, duh. The “OPTIONS” request arrives in |
Support CORS preflight requests with OutOfBlinkCors (fixes issue #3006) A CORS preflight request is an "OPTIONS" request sent to a server prior to a A CORS preflight request will only be sent if certain conditions are met. For CORS preflight functionality is implemented in the network service and will not [1] https://fetch.spec.whatwg.org/#cors-safelisted-method → <<cset acfac2f56b3b (bb)>> |
|
Support CORS preflight requests with OutOfBlinkCors (fixes issue #3006) A CORS preflight request is an "OPTIONS" request sent to a server prior to a A CORS preflight request will only be sent if certain conditions are met. For CORS preflight functionality is implemented in the network service and will not [1] https://fetch.spec.whatwg.org/#cors-safelisted-method → <<cset 4cfacc47431a (bb)>> |
Support CORS preflight requests with OutOfBlinkCors (fixes issue #3006) A CORS preflight request is an "OPTIONS" request sent to a server prior to a A CORS preflight request will only be sent if certain conditions are met. For CORS preflight functionality is implemented in the network service and will not [1] https://fetch.spec.whatwg.org/#cors-safelisted-method → <<cset cc56720bd29a (bb)>> |
…miumembedded#3006) A CORS preflight request is an "OPTIONS" request sent to a server prior to a cross-origin XMLHttpRequest or Fetch request. The server's response determines which HTTP request methods are allowed and supported, and whether credentials such as Cookies and HTTP Authentication should be sent with requests. A CORS preflight request will only be sent if certain conditions are met. For example, it will be sent for requests that have potentially unsafe HTTP methods [1] or request headers [2]. See the NeedsPreflight function in services/network/cors/cors_url_loader.cc for full details. CORS preflight functionality is implemented in the network service and will not be triggered if the client handles the request instead of allowing it to proceed over the network. Since the preflight request itself also runs in the network service it cannot be intercepted by the client. [1] https://fetch.spec.whatwg.org/#cors-safelisted-method [2] https://fetch.spec.whatwg.org/#cors-safelisted-request-header
…miumembedded#3006) A CORS preflight request is an "OPTIONS" request sent to a server prior to a cross-origin XMLHttpRequest or Fetch request. The server's response determines which HTTP request methods are allowed and supported, and whether credentials such as Cookies and HTTP Authentication should be sent with requests. A CORS preflight request will only be sent if certain conditions are met. For example, it will be sent for requests that have potentially unsafe HTTP methods [1] or request headers [2]. See the NeedsPreflight function in services/network/cors/cors_url_loader.cc for full details. CORS preflight functionality is implemented in the network service and will not be triggered if the client handles the request instead of allowing it to proceed over the network. Since the preflight request itself also runs in the network service it cannot be intercepted by the client. [1] https://fetch.spec.whatwg.org/#cors-safelisted-method [2] https://fetch.spec.whatwg.org/#cors-safelisted-request-header
…miumembedded#3006) A CORS preflight request is an "OPTIONS" request sent to a server prior to a cross-origin XMLHttpRequest or Fetch request. The server's response determines which HTTP request methods are allowed and supported, and whether credentials such as Cookies and HTTP Authentication should be sent with requests. A CORS preflight request will only be sent if certain conditions are met. For example, it will be sent for requests that have potentially unsafe HTTP methods [1] or request headers [2]. See the NeedsPreflight function in services/network/cors/cors_url_loader.cc for full details. CORS preflight functionality is implemented in the network service and will not be triggered if the client handles the request instead of allowing it to proceed over the network. Since the preflight request itself also runs in the network service it cannot be intercepted by the client. [1] https://fetch.spec.whatwg.org/#cors-safelisted-method [2] https://fetch.spec.whatwg.org/#cors-safelisted-request-header
Original report by Salvador Diaz Fau (Bitbucket: salvadordf, GitHub: salvadordf).
What steps will reproduce the problem?
What is the expected output? What do you see instead?
In the case of Google.com it should show a QR code and with bitbucket.org it should authenticate the user if the useranme and password were real.
What version of the product are you using? On what operating system?
CEF 85.2.11+g0202816+chromium-85.0.4183.83
Windows 10 64 bits
http://opensource.spotify.com/cefbuilds/cef_binary_85.2.11%2Bg0202816%2Bchromium-85.0.4183.83_windows64_client.tar.bz2
Does the problem reproduce with the cefclient or cefsimple sample application at the same version? How about with a newer or older version?
This issue started with CEF 85.2.9. The previous cefclient version (CEF 84.4.1) worked perfectly.
Does the problem reproduce with Google Chrome at the same version? How about with a newer or older version?
Chrome 85 works correctly.
Workaround :
Run cefclient with this switch --disable-features=OutOfBlinkCors
Related forum thread link :
https://magpcss.org/ceforum/viewtopic.php?f=6&t=17826
The text was updated successfully, but these errors were encountered: