Fetch reports "Already read" when there's a lock |
|||||
Issue descriptionhttp://output.jsbin.com/zogumu/quiet - the error is slightly misleading here. It says the body has already been read but it hasn't, the problem is something has a lock on the stream. If the stream is unlocked, .text() will work fine.
,
Oct 19 2016
,
Oct 19 2017
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. If you change it back, also remove the "Hotlist-Recharge-Cold" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Oct 20 2017
,
Oct 20 2017
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/a72db01caf4bb13900afd7bb7d3ebe505841d618 commit a72db01caf4bb13900afd7bb7d3ebe505841d618 Author: Adam Rice <ricea@chromium.org> Date: Fri Oct 20 12:15:41 2017 fetch API Body: improve exception message when locked When the body stream of a Response is locked but hasn't been read from, use the exception message "bosy stream is locked" rather than "Already read". Also, for the case where it has been read, change the exception message to "body stream already read" for clarity. BUG= 654703 Change-Id: I55e59477281c3e4430748983b8d2b5e82c711cef Reviewed-on: https://chromium-review.googlesource.com/730037 Reviewed-by: Yutaka Hirano <yhirano@chromium.org> Commit-Queue: Adam Rice <ricea@chromium.org> Cr-Commit-Position: refs/heads/master@{#510410} [modify] https://crrev.com/a72db01caf4bb13900afd7bb7d3ebe505841d618/third_party/WebKit/Source/modules/fetch/Body.cpp
,
Oct 20 2017
|
|||||
►
Sign in to add a comment |
|||||
Comment 1 by ji...@warting.se
, Oct 11 2016