On 9/20/13 7:28 AM, Simon Pieters wrote:
(I'm not sure where the spec says that the above case is a network
error, though.)
https://dvcs.w3.org/hg/xhr/raw-file/tip/Overview.html section 4.6.7
lands us in "Otherwise, follow the cross-origin request steps and
terminate the steps for this algori
On Fri, Sep 20, 2013 at 9:06 AM, Hallvord Steen wrote:
> (AFAIK Gecko is the only engine with this behaviour, although I'm not able to
> test IE because I don't have a Win7 or 8 machine and lesser IE versions don't
> work well with the test framework.)
Let's go with network error for now then.
Anne vK:
> Not sure it makes
> sense to return the erroneous redirect response instead, although I
> suppose that might make polyfilling easier if we do it right and
> implementations get all the details correct.
Those two caveats apply to everything, I suppose ;-) Anyway - it's your call
but if
On Fri, Sep 20, 2013 at 7:28 AM, Simon Pieters wrote:
> (I'm not sure where the spec says that the above case is a network error,
> though.)
Once I get to redefining XMLHttpRequest in terms of
http://fetch.spec.whatwg.org/ it would be I think. Not sure it makes
sense to return the erroneous redir
On Fri, 20 Sep 2013 13:20:44 +0200, Hallvord Steen
wrote:
Test case
http://w3c-test.org/web-platform-tests/master/XMLHttpRequest/send-redirect-bogus.htm
has an interesting behaviour in Gecko. Last test fails with output:
assert_equals: expected "" but got "WEBSRT MARKETING"
Test returns
Test case
http://w3c-test.org/web-platform-tests/master/XMLHttpRequest/send-redirect-bogus.htm
has an interesting behaviour in Gecko. Last test fails with output:
assert_equals: expected "" but got "WEBSRT MARKETING"
Test returns a bogus redirect like
HTTP/1.1 303 WEBSRT MARKETING
Location: fo