Client Error Status Codes

This class of status code is intended for cases in which the client seems to have erred. The IPP object SHOULD return a message

containing an explanation of the error situation and whether it is a temporary or permanent condition.

13.1.4.1 client-error-bad-request (0x0400)

The request could not be understood by the IPP object due to

malformed syntax (such as the value of a fixed length attribute whose length does not match the prescribed length for that attribute - see the Implementer’s Guide [ipp-iig] ). The IPP application SHOULD NOT repeat the request without modifications.

13.1.4.2 client-error-forbidden (0x0401)

The IPP object understood the request, but is refusing to fulfill it.

Additional authentication information or authorization credentials will not help and the request SHOULD NOT be repeated. This status

code is commonly used when the IPP object does not wish to reveal exactly why the request has been refused or when no other response is applicable.

13.1.4.3 client-error-not-authenticated (0x0402)

The request requires user authentication. The IPP client may repeat the request with suitable authentication information. If the request already included authentication information, then this status code indicates that authorization has been refused for those credentials.

If this response contains the same challenge as the prior response, and the user agent has already attempted authentication at least once, then the response message may contain relevant diagnostic information. This status codes reveals more information than "client-error-forbidden".

13.1.4.4 client-error-not-authorized (0x0403)

The requester is not authorized to perform the request. Additional authentication information or authorization credentials will not help and the request SHOULD NOT be repeated. This status code is used when the IPP object wishes to reveal that the authentication

information is understandable, however, the requester is explicitly not authorized to perform the request. This status codes reveals more information than forbidden" and not-authenticated".

13.1.4.5 client-error-not-possible (0x0404)

This status code is used when the request is for something that can not happen. For example, there might be a request to cancel a job that has already been canceled or aborted by the system. The IPP client SHOULD NOT repeat the request.

13.1.4.6 client-error-timeout (0x0405)

The client did not produce a request within the time that the IPP object was prepared to wait. For example, a client issued a Job operation and then, after a long period of time, issued a Document operation and this error status code was returned in

response to the Send-Document request (see section 3.3.1). The IPP object might have been forced to clean up resources that had been held for the waiting additional Documents. The IPP object was forced to close the Job since the client took too long. The client SHOULD NOT repeat the request without modifications.

13.1.4.7 client-error-not-found (0x0406)

The IPP object has not found anything matching the request URI. No indication is given of whether the condition is temporary or

permanent. For example, a client with an old reference to a Job (a URI) tries to cancel the Job, however in the mean time the Job might have been completed and all record of it at the Printer has been deleted. This status code, ’client-error-not-found’ is returned indicating that the referenced Job can not be found. This error status code is also used when a client supplies a URI as a reference to the document data in either a Print-URI or Send-URI operation, but the document can not be found.

In practice, an IPP application should avoid a not found situation by first querying and presenting a list of valid Printer URIs and Job URIs to the end-user.

13.1.4.8 client-error-gone (0x0407)

The requested object is no longer available and no forwarding address is known. This condition should be considered permanent. Clients with link editing capabilities should delete references to the

request URI after user approval. If the IPP object does not know or has no facility to determine, whether or not the condition is

permanent, the status code "client-error-not-found" should be used instead.

This response is primarily intended to assist the task of maintenance by notifying the recipient that the resource is intentionally

unavailable and that the IPP object administrator desires that remote links to that resource be removed. It is not necessary to mark all permanently unavailable resources as "gone" or to keep the mark for any length of time -- that is left to the discretion of the IPP object administrator.

13.1.4.9 client-error-request-entity-too-large (0x0408)

The IPP object is refusing to process a request because the request entity is larger than the IPP object is willing or able to process.

An IPP Printer returns this status code when it limits the size of print jobs and it receives a print job that exceeds that limit or when the attributes are so many that their encoding causes the request entity to exceed IPP object capacity.

13.1.4.10 client-error-request-value-too-long (0x0409)

The IPP object is refusing to service the request because one or more of the client-supplied attributes has a variable length value that is longer than the maximum length specified for that attribute. The IPP object might not have sufficient resources (memory, buffers, etc.) to process (even temporarily), interpret, and/or ignore a value larger than the maximum length. Another use of this error code is when the IPP object supports the processing of a large value that is less than the maximum length, but during the processing of the request as a whole, the object may pass the value onto some other system component which is not able to accept the large value. For more details, see the Implementer’s Guide [ipp-iig] .

Note: For attribute values that are URIs, this rare condition is only likely to occur when a client has improperly submitted a request with long query information (e.g. an IPP application allows an user to enter an invalid URI), when the client has descended into a URI "black hole" of redirection (e.g., a redirected URI prefix that points to a suffix of itself), or when the IPP object is under attack by a client attempting to exploit security holes present in some IPP objects using fixed-length buffers for reading or manipulating the Request-URI.

13.1.4.11 client-error-document-format-not-supported (0x040A) The IPP object is refusing to service the request because the

document data is in a format, as specified in the "document-format"

operation attribute, that is not supported by the Printer object.

This error is returned independent of the client-supplied attribute-fidelity". The Printer object MUST return this status code, even if there are other attributes that are not supported as well, since this error is a bigger problem than with Job Template attributes.

13.1.4.12 client-error-attributes-or-values-not-supported (0x040B) In a create request, if the Printer object does not support one or more attributes, attribute syntaxes, or attribute values supplied in the request and the client supplied the "ipp-attributes-fidelity"

operation attribute with the ’true’ value, the Printer object MUST return this status code. For example, if the request indicates ’ iso-a4’ media, but that media type is not supported by the Printer object. Or, if the client supplies an optional attribute and the attribute itself is not even supported by the Printer. If the attribute-fidelity" attribute is ’false’, the Printer MUST ignore or substitute values for unsupported attributes and values rather than

For any operation where a client requests attributes (such as a Jobs, Get-Printer-Attributes, or Get-Job-Attributes operation), if the IPP object does not support one or more of the requested

attributes, the IPP object simply ignores the unsupported requested attributes and processes the request as if they had not been

supplied, rather than returning this status code. In this case, the IPP object MUST return the attributes’ status code and MAY return the unsupported attributes as values of the "requested-attributes" in the Unsupported Attributes Group (see section 13.1.2.2).

13.1.4.13 client-error-uri-scheme-not-supported (0x040C)

The type of the client supplied URI in a Print-URI or a Send-URI operation is not supported.

13.1.4.14 client-error-charset-not-supported (0x040D)

For any operation, if the IPP Printer does not support the charset supplied by the client in the "attributes-charset" operation

attribute, the Printer MUST reject the operation and return this status and any ’text’ or ’name’ attributes using the ’utf-8’ charset (see Section 3.1.4.1).

13.1.4.15 client-error-conflicting-attributes (0x040E)

The request is rejected because some attribute values conflicted with the values of other attributes which this specification does not permit to be substituted or ignored.