TakeStartLine and TakeMessageHeaders can spin without awaiting given incomplete data #1095

halter73 · 2016-09-09T00:00:30Z

Due to a bad "examined" parameter being passed to "SocketInput.ConsumingComplete", "await SocketInput" won't actually await for an incomplete start line or header. This does not affect 1.0.0/1.0.1.

halter73 · 2016-09-09T00:01:05Z

#1094

halter73 added the bug label Sep 9, 2016

halter73 added this to the 1.1.0 milestone Sep 9, 2016

halter73 assigned cesarblum Sep 9, 2016

cesarblum mentioned this issue Sep 9, 2016

Ensure ConsumingComplete() is always called with the furthest examined position (#1095) #1094

Merged

cesarblum pushed a commit that referenced this issue Sep 11, 2016

Always call ConsumingComplete() with furthest examined position (#1095).

8c51340

cesarblum added the 3 - Done label Sep 11, 2016

cesarblum closed this as completed Sep 11, 2016

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

TakeStartLine and TakeMessageHeaders can spin without awaiting given incomplete data #1095

TakeStartLine and TakeMessageHeaders can spin without awaiting given incomplete data #1095

halter73 commented Sep 9, 2016

halter73 commented Sep 9, 2016

TakeStartLine and TakeMessageHeaders can spin without awaiting given incomplete data #1095

TakeStartLine and TakeMessageHeaders can spin without awaiting given incomplete data #1095

Comments

halter73 commented Sep 9, 2016

halter73 commented Sep 9, 2016