Bug 116579
| Summary: | [Mac] XMLHttpRequest timeout is accounted for incorrectly - should be total time, not inactive time | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Alexey Proskuryakov <ap> |
| Component: | XML | Assignee: | Nobody <webkit-unassigned> |
| Status: | NEW | ||
| Severity: | Normal | CC: | d-r, youennf |
| Priority: | P2 | ||
| Version: | 528+ (Nightly build) | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| See Also: | https://bugs.webkit.org/show_bug.cgi?id=98156 | ||
Alexey Proskuryakov
XHR timeout attribute specifies how long the request may take. (At least) the Mac implementation is different, it only triggers a timeout if the connection is idle for this long.
"Can be set to a time in milliseconds. When set to a non-zero value will cause fetching to terminate after the given time has passed."
"This implies that the timeout attribute can be set while fetching is in progress. If that occurs it will still be measured relative to the start of fetching."
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
youenn fablet
This might be covered as part of bug 98156.
Alexey Proskuryakov
Sounds like it would be, but only for async requests, not for sync ones.
youenn fablet
(In reply to comment #2)
> Sounds like it would be, but only for async requests, not for sync ones.
Right.
For Soup and CURL, async calls to the underlying libraries are made within a sync loop.
I do not know whether this is actually worth the effort but Mac may use a similar strategy.