|
|
||||||||||||
Issue descriptionhttp://w3c-test.org/cors/allow-headers.htm http://w3c-test.org/cors/origin.htm http://w3c-test.org/cors/preflight-cache.htm http://w3c-test.org/cors/redirect-preflight-2.htm http://w3c-test.org/cors/redirect-userinfo.htm http://w3c-test.org/cors/remote-origin.htm These failures need analysis, but may point to low-hanging fruit for improving interop. Judgement is required, the failures may be entangled with spec issues. Note: Results may have changed in the interim. , Sep 30 2016
, Sep 30 2016
, Dec 6 2016
Has anyone from the security team had a chance to look at these tests? If they are legitimate failures, should we triage this bug to an eventual work backlog? , Jan 9 2017Re-ping to see if we need any more information to be able to triage this issue? , Feb 6 2017
@mkwst ping :) , Feb 6 2017
making mkwst owner instead of status :P , Feb 6 2017
, Feb 23 2017
CCing loading folks who might be interested in poking at these. , Nov 10 2017
, Feb 18 2018
, Oct 12Two of these fail *only* in Chrome and pass also in Safari, in addition to Firefox and Edge: https://wpt.fyi/results/cors/allow-headers.htm?products=chrome%5Bexperimental%5D,edge%5Bstable%5D,firefox%5Bstable%5D,safari%5Bstable%5D&sha=434ca47448https://wpt.fyi/results/cors/remote-origin.htm?products=chrome%5Bexperimental%5D,edge%5Bstable%5D,firefox%5Bstable%5D,safari%5Bstable%5D&sha=434ca47448 , Oct 17
, Oct 18
|
||||||||||||
►
Sign in to add a comment |
||||||||||||
Comment 1 by foolip@chromium.org, Sep 30 2016