<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><br><div><div>On Jul 9, 2013, at 4:30 AM, Itamar Turner-Trauring <<a href="mailto:itamar@itamarst.org">itamar@itamarst.org</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div style="font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;">On 07/09/2013 04:04 AM, Rob Meijer wrote:<br><blockquote type="cite">3) When the token does not check out, or the connection to the server<br>fails, it remains a mystery to me how I should throw an error in such a<br>way that it allows me to send a proper error message to the client, while<br>not having to first accept the whole large file. That is, it seems rather<br>silly that I would know things failed after the first POST body chunk, but<br>would have to wait for and accept hundreds of megabytes or maybe even a<br>few gigabytes of post data before I can notify the client that something<br>went wrong.<br><br></blockquote>HTTP clients can send a "Expects: 100-continue" header (or something like that), which tells the server it should give an early rejection or acceptance before the client sends the data, in *addition* to the final response. You would still need to write some code to support this, but it is possible.<br></div></blockquote></div><br><div>FYI, it's "<b>Expect:</b> 100-continue" ;-). <<a href="http://www.w3.org/Protocols/rfc2616/rfc2616-sec8">http://www.w3.org/Protocols/rfc2616/rfc2616-sec8</a>>.</div><div><br></div><div>-glyph</div></body></html>