Descriptionnet/http: remove more garbage from chunk reading
Noticed this while closing tabs. Yesterday I thought I could
ignore this garbage and hope that a fix for issue 2205 handled
it, but I just realized that's the opposite case,
string->[]byte, whereas this is []byte->string. I'm having a
hard time convincing myself that an Issue 2205-style fix with
static analysis and faking a string header would be safe in
all cases without violating the memory model (callee assumes
frozen memory; are there non-racy ways it could keep being
modified?)
Patch Set 1 #Patch Set 2 : diff -r a26a8ada8f6e https://go.googlecode.com/hg/ #Patch Set 3 : diff -r a26a8ada8f6e https://go.googlecode.com/hg/ #
Total comments: 1
Patch Set 4 : diff -r 3d3b1e3f5268 https://go.googlecode.com/hg/ #
Total comments: 8
Patch Set 5 : diff -r a070de932857 https://go.googlecode.com/hg/ #Patch Set 6 : diff -r 73c62d1bf08c https://go.googlecode.com/hg/ #
MessagesTotal messages: 15
|