Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Relationship between XHR timeout and network timeout #96

Open
youennf opened this issue Oct 28, 2016 · 1 comment
Open

Relationship between XHR timeout and network timeout #96

youennf opened this issue Oct 28, 2016 · 1 comment

Comments

@youennf
Copy link

youennf commented Oct 28, 2016

XHR allows setting timeout.
There is probably interoperability when timeout is set.
It is unclear what happens when no timeout is set.

In WebKit, when timeout is set, the network IDLE timeout is disabled.
When no timeout is set, the default network IDLE timeout of 60 seconds may kick in.

Should there be a default XHR timeout value?

Related to fetch, no timeout mechanism is defined.
In WebKit, this would mean that the default network IDLE timeout of 60 seconds cannot be controlled by web developers.

@annevk
Copy link
Member

annevk commented Oct 31, 2016

Adding API surface to fetch() for timeouts is whatwg/fetch#20. Defining a default network timeout might be a thing we need to do at some point, but I think for now I'm okay with leaving that up to user agents unless we've found issues with that.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

No branches or pull requests

2 participants