Closed ghost closed 7 years ago
Which browser are you seeing this in? That xhr should never actually be sent; it's created only to see what features are provided by the XMLHttpRequest object.
I am using chrome.
On Nov 18, 2016 2:45 PM, "John Hiesey" notifications@github.com wrote:
Which browser are you seeing this in? That xhr should never actually be sent; it's created only to see what features are provided by the XMLHttpRequest object.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/jhiesey/stream-http/issues/60#issuecomment-261661974, or mute the thread https://github.com/notifications/unsubscribe-auth/AEe_Xn_MGpuMbzFWHZDHV_ash01bw5yvks5q_iqCgaJpZM4K27tW .
Same issue with last version of Chrome, no issue with last version of Firefox.
this is throwing for me, when using electron with a content-security-policy https://github.com/ssbc/patchwork/issues/431
@jhiesey New Chrome versions will throw even on open. I don't know which version exactly changed this behavior.
All Webpack 1 users are affected by this issue.
Hey, any progress with this issue ?
This should be fixed by #61
Will be included in version 2.6.0
@jhiesey Thanks for the update. Btw when is the next version going to be released?
Should be within the next 24 hours. I'm trying to get the tests to pass, but they're being flaky due to #63
My company's web stack uses CORS. Merely importing stream-http causes a request to be made to example.com, which violates CORS and therefore causes the import to fail. In fact, I'm not importing stream-http directly, I'm importing fetch, so I can't simply try/catch the import or anything like that.
The error appears on the line:
Failed on xhr.open('GET', global.location.host ? '/' : 'https://example.com')
So this is related to the previous issue.