[cups.bugs] [MOD] STR #2587: cupsd will no longer seems to accept requests from OLD cups clients
Jon Peatfield
J.S.Peatfield at damtp.cam.ac.uk
Mon Nov 12 08:47:20 PST 2007
On Thu, 8 Nov 2007, Michael Sweet wrote:
> [STR Closed w/o Resolution]
>
> If the locale uses UTF-8, that character set will be passed to the CUPS
> server and it will work.
That doesn't _seem_ to happen if I test it thus:
$ LANG="en_US.UTF-8" CUPS_SERVER=ganglia lpq
lpq: get-jobs failed: client-error-bad-request
and the server still logs the request as having the illegal charset
iso-8859-1. That is from a machine using cups-1.1.17 - for some reason it
seems to be always using iso-8859-1 though I don't understand why.
> CUPS 1.3.x only supports US-ASCII and UTF-8. Adding support for other
> character sets is not feasible from both a memory and performance
> standpoint, and this issue is easily fixed by upgrading to a more recent
> version of CUPS or using a UTF-8 locale.
Sadly we need to support clients were we can't force the users to upgrade
their machines. This seems to be a *new* feature in 1.3.4 - 1.3.3 didn't
reject the jobs/requests.
If cups-1.3.x is not intended to accept jobs/requests from cups-1.1.x
perhaps a big warning is needed to alert people who have a mixture of
clients of different ages.
--
Jon Peatfield, Computer Officer, DAMTP, University of Cambridge
Mail: jp107 at damtp.cam.ac.uk Web: http://www.damtp.cam.ac.uk/
More information about the cups
mailing list