Re: Regarding IPP headers

Hi,

The program to forward some local port at the client end to the server port 631 
works fine. Able to print too. But we only get this(even if we give some print 
command):

Client:
POST / HTTP/1.1
Content-Length: 238

Client:
Content-Type: application/ipp
Host: 0.0.0.0



@
Server:
HTTP/1.1 200 OK

Server:
Date: Mon, 25 Oct 2004 09:04:43 GMT

Server:
Server: CUPS/1.1

Server:
Connection: Keep-Alive
Keep-Alive: timeout=60
Content-Language: en_US
Content-Type: application/ipp; charset=utf-8
Content-Length: 977




Client:
POST / HTTP/1.1
Content-Length: 238

Client:
Content-Type: application/ipp
Host: 0.0.0.0



@
Server:
HTTP/1.1 200 OK
Date: Mon, 25 Oct 2004 09:04:45 GMT
Server: CUPS/1.1
Connection: Keep-Alive
Keep-Alive: timeout=60
Content-Language: en_US
Content-Type: application/ipp; charset=utf-8
Content-Length: 75




xterm

where and how are the filename / username etc are being passed?

Could you tell us how to get those details.

Thank You,
-Riyaz



p.mdriyaz wrote:
> Hi,
> I would also like to know how the ipp headers are terminated.(what 
> character/sequence of characters)?
> Thank you,
> -Riyaz
>
> p.mdriyaz wrote:
> > Hi,
> >
> > We have a set up network printing here , with the quota mangement is being 
> > done by pykota. Cups registers the print job with the user name with which  
> > the person has logged in, hence there is a problem when many people use the 
> > same user name.
> >
> > So we thought we could write a small prog that would run on the users 
> > computer and listen at some port x. In cups config we say browse port x.
> > The prog listening at port x gets the application level (ipp) data and 
> > searches for the Username and replaces it with the unique id and sends it 
> > to some port on the server say 'y'.
> >
> > The program listening at y forwards the data to port 631 on the server.
> >
> > I would like to know if this would work? and if yes is there any thing 
> > specific that needs to be done.
> >
> > Thank you,
> > -Riyaz
>