System Administration Guide: Solaris Printing

How the IPP Listening Service Works

The IPP Listening Service implementation (server-side support) is embedded under the Apache web server. The web server receives IPP operations through HTTP POST requests. When an HTTP POST request is received, it is then passed on to the Apache IPP module (mod_ipp.so). Based on configuration, the Apache web service can also provide an authentication service and be used for encryption between print client and server. The listening service runs as it's own dedicated instance of Apache.

This process is as follows:

  1. An IPP request is sent from the client to the server.

  2. The Apache web server accepts the connection.

  3. The Apache web server then hands the connection to mod_ipp.

  4. mod_ipp passes the connection and configuration data to libipp-listener.

  5. libipp-listener reads the request by using lipipp-core.

  6. libipp-listener dispatches the request to the operation handler located in lipipp-listener.

  7. The operation handler converts the request to a PAPI call and then makes the call.

  8. The PAPI call is translated to a print service specific request by using psm-lpsched.

  9. The print service responds to the request.

  10. The psm-lpsched command converts the response to PAPI results.

  11. The libpapi operation returns to the libipp-listener operation handler.

  12. The libipp-listener operation handler passes results to dispatcher.

  13. The libipp-listener dispatcher writes results to client by using the libipp-core library.

  14. The dispatcher returns the mod_ipp entry point.