New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cannot print to Xerox Phaser 8200 via IPP #716
Comments
CUPS.org User: mike Please try the attached patch instead, which avoids using goto... |
CUPS.org User: mike Fixed in CVS - the anonymous CVS repository will be updated at midnight EST. |
"cups-continue.patch": --- cups-1.1.20/cups/util.c.continue 2004-05-11 17:52:08.000000000 +0100
|
"str716.patch": Index: util.cRCS file: /development/cvs/cups/cups/util.c,v
if (ippWrite(http, request) != IPP_ERROR)
|
Version: 1.1.20
CUPS.org User: twaugh.redhat
See https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=122352.
The Xerox Phaser 8200 IPP implementation uses Spyglass_MicroServer/2.01FC1, which has odd (but compliant) behaviour regarding HTTP/1.1 100 Continue result codes. You can see a libpcap-style traffic capture log at the Bugzilla report showing this in detail.
A 100 result code is always sent by this IPP implementation after it has received the HTTP headers, but slowly enough that it is not received until after the first write from the job file.
The code (cups/util.c:cupsDoFileRequest) goes:
Since there is no final result code to read we end up stuck in recv().
Here is a patch to handle mid-request Continue result codes.
The text was updated successfully, but these errors were encountered: