curl: HTTP/1.1 100 CONTINUE and multipart/form-data POST
I’m working on a REST interface at the moment, and there’s nothing I need more than a quick utility to test out various functions. Curl fills this role perfectly, but I have run into a strange problem that interferes with multipart/form-data form POSTing. Let me explain some of the evidence I’ve collected, as well as tell you a workaround I learned from an IRC conversation. In the end, this comes down to the HTTP 1.1 100 CONTINUE response code, which plays a critical role in HTTP 1.1 POST.
Recent Comments