Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 978387

Summary: Bad IPP responses with version 2.0 (collection handling bug)
Product: Red Hat Enterprise Linux 6 Reporter: Tim Waugh <twaugh>
Component: cupsAssignee: Tim Waugh <twaugh>
Status: CLOSED ERRATA QA Contact: qe-baseos-daemons
Severity: unspecified Docs Contact:
Priority: high    
Version: 6.4CC: psklenar
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: cups-1.4.2-53.el6 Doc Type: Bug Fix
Doc Text:
When a client requests IPP version 2.0, incorrect IPP data would be sent when attributes were part of a collection. A fix for this has been backported from a later version.
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-10-14 07:31:14 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 978427    
Attachments:
Description Flags
cups-str3521.patch none

Description Tim Waugh 2013-06-26 13:58:28 UTC
Description of problem:
When using IPP/2.0 (from e.g. Fedora 19), a bug in the IPP writing code for 'collection' attribute types can cause incorrect data to be sent back in response to, for example, a printer attributes query.

In particular, the IPP data sent is shorter than the HTTP Content-Length header advertises, causing the IPP/2.0 client to wait for the rest of the data and, since it is not forthcoming, time out.

Version-Release number of selected component (if applicable):
cups-1.4.2-50.el6_4.4

How reproducible:
100%

Steps to Reproduce:
1.From Fedora 19: lpstat -h theserver/version=2.0 -s

Actual results:
60s delay for each IPP request.

Expected results:
No delay.

Comment 1 Tim Waugh 2013-06-26 14:00:34 UTC
Created attachment 765612 [details]
cups-str3521.patch

Comment 2 RHEL Program Management 2013-10-13 23:26:39 UTC
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated
in the current release, Red Hat is unable to address this
request at this time.

Red Hat invites you to ask your support representative to
propose this request, if appropriate, in the next release of
Red Hat Enterprise Linux.

Comment 7 errata-xmlrpc 2014-10-14 07:31:14 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHSA-2014-1388.html