/servlet/IPPServlet/vega-lp
/servlet/IPPServlet/pp4019
both cause the web server on carlk to invoke servlet IPPServlet. IPPServlet uses the path info from the Request-URI to determine if the target output device is "vega-lp" or "pp4019".
>
> > But the final decision was that the HTTP Request-URI and the embedded
> > "printer-uri" MUST be the SAME. Therefore the IPP Object that receives
> > the request must be the target.
>
> Did we actually come to a final decision? I didn't read that we had.
> (Maybe I'm missing a message or two on this subject?)
>
In http://www.findmail.com/list/ipp/mg771994797.html, Robert Herriot wrote:
> Randy suggests that the value of job-uri/printer-uri could differ from the request-uri on the HTTP Request-Line, but the model has no such concept. So unless there are strong arguments to the contrary, the protocol document will state that the request-uri has the same value as the printer-uri/job-uri in the operation.
Then Randy agreed, and the thread ended.
>
>
> > There could be a problem if a proxy rewrites the Request-URI in any way.
>
> Yeah, this worries me, too. We definitely need some serious
> implementation experience to better understand the ramifications
> of this situation.
>
> ...jay
>
> ----------------------------------------------------------------------
> -- JK Martin | Email: jkm@underscore.com --
> -- Underscore, Inc. | Voice: (603) 889-7000 --
> -- 41C Sagamore Park Road | Fax: (603) 889-2699 --
> -- Hudson, NH 03051-4915 | Web: http://www.underscore.com --
> ----------------------------------------------------------------------
>
>