<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><div>On Jan 24, 2011, at 8:19 PM, Duncan McEwan wrote:</div><blockquote type="cite"><div><blockquote type="cite"><font class="Apple-style-span" color="#000000">...</font></blockquote><blockquote type="cite">Correct, but the origin server cannot respond with a *successful* status<br></blockquote><blockquote type="cite">until it has received *all* of the request body (since successful<br></blockquote><blockquote type="cite">statuses allow for Keep-Alive and pipelining; failure status codes cause<br></blockquote><blockquote type="cite">the connection to close...)<br></blockquote><br>OK - as I said, I'm not familiar with all the details of the HTTP and IPP protocols and so I'm quite likely missing something here. But it seems to me that the origin server *should have* received a complete request body since my tcpdump packet trace shows the HTTP request header and IPP request were both transmitted by CUPS without waiting for the 100-continue response.<br></div></blockquote><div><br></div><div>The strategy CUPS uses is to periodically check for a response as the request and request body are sent. The 1 second wait comes after the IPP message is sent but before any document data is sent.</div><div><br></div>In any case, if the printer sends a successful response before getting the entire message body, it isn't following RFC 2616...</div><div><br></div><div>That said...</div><div><br><blockquote type="cite"><div><font class="Apple-style-span" color="#540000">...<br></font>If this is the printers fault, would an acceptable workaround be a configuration<br>option to tell CUPS not to expect the "100 Continue" response for certain<br>(broken) printers?<br></div></blockquote></div><div><br></div>CUPS currently doesn't offer a configurable option for this, but does go into a "no expect" mode if the printer fails to respond the first time we send a request.<div><br><div>
<span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Monaco; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; "><span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Monaco; font-size: medium; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; "><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Monaco; font-size: medium; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; "><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div>________________________________________________________________________</div><div>Michael Sweet, Senior Printing System Engineer, PWG Chair</div></div></span></div></span></span>
</div>
<br></div></body></html>