Bug#704238: Need to document the CUPS client's new server-version option
On 2013-06-20 10:41:56 -0400, Michael Sweet wrote:
> On 2013-06-06, at 2:59 AM, Didier 'OdyX' Raboud <odyx@debian.org> wrote:
> >> ...
> >> ServerName cups.example.com/version=1.1
> >
> > Indeed. That's confirmed to address Vincent's issue. Although it's kinda
> > surprising that it's impossible to detect that at runtime, but that's an
> > upstream decision…
>
> It isn't impossible, but it can be unreliable and is problematic for
> existing users of the cupsSendRequest/cupsGetResponse APIs - they
> have to handle the downgrading themselves.
>
> We *did* try tracking the supported IPP version in the first version
> of the patch for this issue, but it didn't work reliably. Forcing
> the issue in client.conf seemed the safest approach.
OK. So, the protocol doesn't specify a way to ask the server
what version is running?
However would it be possible to output a real error message?
The errors I get
ypig:~> lpq -P lipucb-mono-1
lpq: Unknown destination "lipucb-mono-1".
ypig:~> lpstat -a
lpstat: Bad Request
are quite uninformative, in particular the first one.
There's a difference between having an unknown printer name
(say, like in "lpq -P does-not-exist") and having something
wrong in the communication with the server.
--
Vincent Lefèvre <vincent@vinc17.net> - Web: <http://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <http://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)
Reply to: