[cups.general] Excessive Get-Printer-Attributes in CUPS

[Jeff Hardy]

On Tue, 2007-07-24 at 12:40 -0700, Kurt Pfeifle wrote:
> Jeff Hardy wrote:
> 
> > These are all raw queues, and I had assumed that
> > 'client-error-not-found' would be expected for any queue without a PPD.
> > Is that correct?
> 
> I don't think that raw queues would return for "Get-Printer-Attributes"
> always a 'client-error-not-found' (even 'raw' queues do have attributes).
> 

Apologies for responding to an old post, but I am still seeing the
issue.  I had debugging turned on trying to track down something
unrelated, and found this:

D [17/Sep/2007:10:29:52 -0400] cupsdAcceptClient: skipping getpeercon()
D [17/Sep/2007:10:29:52 -0400] cupsdAcceptClient: 11 from localhost
(Domain)
D [17/Sep/2007:10:29:52 -0400] cupsdReadClient: 11 POST / HTTP/1.1
D [17/Sep/2007:10:29:52 -0400] cupsdAuthorize: No authentication data
provided.
D [17/Sep/2007:10:29:52 -0400] Get-Printer-Attributes
ipp:///printers/printers
D [17/Sep/2007:10:29:52 -0400] Get-Printer-Attributes
client-error-not-found: The printer or class was not found.
D [17/Sep/2007:10:29:52 -0400] cupsdProcessIPPRequest: 11
status_code=406 (client-error-not-found)
D [17/Sep/2007:10:29:52 -0400] cupsdCloseClient: 11


The path ipp:///printers/printers definitely does not exist.  Curious.

-Jeff

-- 
Jeff Hardy
Systems Analyst
hardyjm at potsdam.edu