IPP Mail Archive: RE: IPP> Re: Implications of introducing new scheme and

RE: IPP> Re: Implications of introducing new scheme and

Robert Herriot (robert.herriot@Eng.Sun.COM)
Mon, 01 Jun 1998 17:01:29 -0700

--=====================_17590854==_.ALT
Content-Type: text/plain; charset="us-ascii"

I have done a few tests with the Java WebServer to see how it works with an
IPP scheme. The results are mixed.

I dicovered that the request line has to be of the form:
POST /servlet/printServer?killtree HTTP/1.0

and the POST fails if it of the form:
POST http://woden/servlet/printServer?killtree HTTP/1.0

I found that I can change HTTP/1.0 to IPP/1.0 and things continue to work.
The method getProtocol returns 'IPP/1.0' instead of 'HTTP/1.0', but the
value of getScheme remains 'http' regardless of the protocol.

Since there is no way to specify the scheme, except implicitly in the
protocol name, the server seems to assume the scheme is http regardless of
protocol.

This indicates to me that there is some danger in changing to an IPP scheme
if we still expect things to work with web servers.

This also raises an important question. If we are changing to an "ipp"
scheme and a different port, then we have fundamentally changed the protocol
and that opens up many issues, such as

1) do we need for HTTP request line and headers or is everything in IPP?
2) do we need MIME syntax for wrapping the application/ipp?
3) should we add separate port for sending data since we are no longer
dependent on HTTP?

--=====================_17590854==_.ALT
Content-Type: text/html; charset="us-ascii"


I have done a few tests with the Java WebServer to see how it works with an
IPP scheme.  The results are mixed.

I dicovered that the request line has to be of the form:
     POST /servlet/printServer?killtree HTTP/1.0

and the POST fails if it of the form:
     POST http://woden/servlet/printServer?killtree HTTP/1.0

I found that I can change HTTP/1.0 to IPP/1.0 and things continue to work. 
The method getProtocol returns 'IPP/1.0' instead of 'HTTP/1.0', but the
value of getScheme remains 'http' regardless of the protocol.  

Since there is no way to specify the scheme, except implicitly in the
protocol name, the server seems to assume the scheme is http  regardless of
protocol.

This indicates to me that there is some danger in changing to an IPP scheme
if we still expect things to work with web servers.

This also raises an important question. If we are changing to an "ipp"
scheme and a different port, then we have fundamentally changed the protocol
and that opens up many issues, such as

    1) do we need for HTTP request line and headers or is everything in IPP?
    2) do we need MIME syntax for wrapping the application/ipp?
    3) should we add separate port for sending data since we are no longer dependent on HTTP?

--=====================_17590854==_.ALT--