I thought that was part of the IPP 1.0 spec? Perhaps it was just
interpreted by some client implementers to mean that it could optionally
arrive after a request, but not at other times? If so, a little additional
clarification might be good. Since having one arrive doesn't require any
action on the part of the client, and it's not guaranteed to arrive from all
server, it's essentially a no-op, and when I wrote mine I just set it up to
ignore it whenever it arrived.
-- Mike "if that's wrong, please let me know!" Bartman --
> -----Original Message-----
> From: Zehler, Peter [mailto:Peter.Zehler at usa.xerox.com]
> Sent: Thursday, October 26, 2000 2:41 PM
> To: IPP Discussion List (E-mail)
> Subject: IPP> Bake Off 3 issue 1
>>> All,
> BO3-1: IPP Client failed when an unexpected HTTP "100 continue" was
> received. Some printers sent a "100 continue" even before
> the Client sent a
> request.
> Proposed Resolution: An IPP Client must accept
> and handle an
> HTTP "100 continue" whenever it is encountered.
>>> Peter Zehler
> XEROX
> Xerox Architecture Center
> Email: Peter.Zehler at usa.xerox.com> Voice: (716) 265-8755
> FAX: (716) 265-8792
> US Mail: Peter Zehler
> Xerox Corp.
> 800 Phillips Rd.
> M/S 139-05A
> Webster NY, 14580-9701
>>