Join GitHub today
GitHub is home to over 36 million developers working together to host and review code, manage projects, and build software together.
Sign upnet/http: something about 100-continue #9735
Comments
adg
changed the title
Expect: 100-continue Doubt!!!
net/http: something about 100-continue
Jan 30, 2015
This comment has been minimized.
This comment has been minimized.
|
I'm having trouble understanding your problem. Can you rephrase? |
This comment has been minimized.
This comment has been minimized.
|
Duplicate of #3665? |
rsc
assigned
bradfitz
Apr 10, 2015
rsc
added this to the Go1.5Maybe milestone
Apr 10, 2015
This comment has been minimized.
This comment has been minimized.
|
I think this is a duplicate. Any use of Expect: 100-continue in client code is currently not going to work the way expected and OP calls this out immediately. |
This comment has been minimized.
This comment has been minimized.
|
Closing as duplicate of #3665 |
bradfitz
closed this
Jun 24, 2015
golang
locked and limited conversation to collaborators
Jun 25, 2016
gopherbot
added
the
FrozenDueToAge
label
Jun 25, 2016
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
gzw13999 commentedJan 30, 2015
If client http header contain Expect: 100-continue
client post multipart/form-data Sometimes there will be
"multipart: Part Read: WSARecv tcp ..138.250:80: i/o timeout" ParseMultipartForm(102400) -> /mime/multipart/multipart.go 239
This is immediately returned error.
Did not arrive ReadTimeout
The same service, the same machine, open the IIS running do not have this problem.