mod_ipp - Embedded Internet Print Protocol (IPP) listener for the Apache HTTP server
/usr/apache/libexec/mod_ipp.so
The mod_ipp module implements RFCs 2910 and 2911 to provide an IPP handling service for the Apache HTTP server. When loaded on the Apache server, mod_ipp processes all HTTP requests with MIME types of application/ipp. The mod_ipp module also processes additional configuration directives to enable or disable portions of the protocol support.
The following is a list of configuration directives that apply to the Apache IPP Listening service:
The values true, yes, on, enable are considered to be synonymous and will enable support for the named operation. All other values will disable support for the named operation.
The following is a list of IPP handling service operations:
print-job
print-uri
validate-job
create-job
get-jobs
get-printer-attributes
pause-printer
resume-printer
purge-jobs
send-document
send-uri
cancel-job
get-job-attributes
hold-job
release-job
restart-job
all
required
Example 1 Using a Configuration File to Start a Standalone Apache Server
The following configuration file can be used to start a standalone Apache server to respond to IPP request sent to port 631.
ServerType standalone ServerRoot "/usr/apache" PidFile /var/run/httpd-standalone-ipp.pid ErrorLog /var/lp/logs/ipp-errors Timeout 300 KeepAlive On MaxKeepAliveRequests 100 KeepAliveTimeout 15 MinSpareServers 1 MaxSpareServers 3 StartServers 1 MaxClients 150 MaxRequestsPerChild 0 LoadModule ipp_module libexec/mod_ipp.so ClearModuleList AddModule mod_ipp.c AddModule mod_so.c Port 631 User lp Group lp ServerAdmin lp@localhost DefaultType application/ipp <IFModule mod_app> <Location /> ipp-operation all on </Location> </IFModule mod_app>
A more restrictive configuration might include the following parameters:
<IFModule mod_app> <Location /> ipp-operation all offn ipp-operation required on </Location> </IFModule mod_app>
See attributes(5) or descriptions of the following attributes:
|
man(1), catman(1M), attributes(5)
Herriot, R., Ed., Butler, S., Moore, P., Turner, R., Wenn, J. RFC 2910, Internet Printing Protocol/1.1: Encoding and Transport. Network Working Group. September 2000.
Hastings, T., Ed., Herriot, R., deBry, R., Isaacson, S., Powell, P. RFC 2911, Internet Printing Protocol/1.1: Model and Semantics. Network Working Group. September 2000.
Configuration file directives are processed in the order listed in the config file. The default behavior is to enable support for all operations implemented in the mod_ipp Apache module.
Since the Apache IPP listening service implements some capabilities that are more of operator features, it may not be desirable to enable all IPP operations without requiring user authentication on the Apache listening service.
The following is an example of a more reasonable configuration for Apache IPP servers without user authentication enabled:
ipp-operations all disabled ipp-operations required enabled
The printers and jobs available under this service can be accessed using URIs of the following form:
printer: http://server[:port]/printers/{queue} ipp://server[:port]/printers/{queue} job: http://server[:port]/printers/{queue}/{job-id} ipp://server[:port]/printers/{queue}/{job-id}
631 is the default IPP port and implied when the URI scheme is ipp. However, some client implementations do not recognize the ipp URI scheme and require http://server:631/... instead. For example, Microsoft's IPP client implementation does not recognize the ipp scheme.
In addition to the documentation and man pages included with Solaris, more information is available at http://www.apache.org
The httpd(8) man page and other Apache man pages are provided with the programming modules. To view the Apache manual pages with the man command, add /usr/apache/man to the MANPATH environment variable. See man(1) for more information. Running catman(1M) on the Apache manual pages is not supported.
Закладки на сайте Проследить за страницей |
Created 1996-2024 by Maxim Chirkov Добавить, Поддержать, Вебмастеру |