[cups.bugs] [MOD] STR #2587: cupsd will no longer seems to accept requests from OLD cups clients

[Jon Peatfield]

DO NOT REPLY TO THIS MESSAGE.  INSTEAD, POST ANY RESPONSES TO THE LINK BELOW.

[STR New]

I just built cups 1.3.4 to test if it fixes a problem that we see, but we
have a number of old machines (not all under our control) running old
versions of cups.

>From a linux box running cups 1.1.17 all jobs are rejected. e.g.

$ CUPS_SERVER=ganglia lpr -Pbcopy /etc/motd  
lpr: unable to print file: client-error-bad-request

and the server (ganglia) logs:

....
D [08/Nov/2007:06:06:53 +0000] cupsdReadClient: 13 POST / HTTP/1.1
D [08/Nov/2007:06:06:53 +0000] cupsdAuthorize: No authentication data
provided.
E [08/Nov/2007:06:06:53 +0000] Unsupported character set "iso-8859-1"!
....

lpq etc also fails and the server logs similar messages.

It doesn't _seem_ to matter what LANG/locale is set on the client, it
always seems to fall foul of the charset.  This seems to be a change since
1.3.3 and the fix for STR #2537 seems to be the cause - which only allows
us-ascii or utf-8.  I really don't understand where iso-8859-1 is comming
from we normally ignore such things setting LANG to 'C' to use the old
ascii rules...

Is there a way to cause older cups clients to send a valid charset?
Can we configure a server to be lax(er) when accepting jobs from old
clients?

[ Well clearly I could undo the part of #2537 which enforces the charset
but that isn't very nice... ]

 -- Jon

Link: http://www.cups.org/str.php?L2587
Version: 1.3.4