HTTP error codes

Use the codes and explanations to understand and correct errors that can be caused when accessing HTTPS resources from the IBM® MQ client library (for example, CCDTURL).

These tables document error codes, in decimal form, that are displayed in message AMQ9795E.

Table 1. Error codes for HTTP errors
Error code (decimal)	Explanation	Response
101	The URL that was specified is too long.	The URL that was provided for a remote resource (for example, the CCDTURL property) exceeds the maximum path length for this operating system.
102	HTTPS initialization failed.	There was a problem initializing the HTTP communication library. This error is usually accompanied by other error messages that indicate the root cause. If required, contact IBM support.
103	There was a communication error with the remote host.	See additional information in the message to diagnose and correct the failure.
104	The remote file or URL was not found.	See additional information in the message to diagnose and correct the failure.
105	The certificate does not belong to the specified host.	Ensure that the distinguished name in the HTTP server’s certificate matches the hostname that is specified. If you are intentionally using a certificate that does not match, you can reduce the level of verification by using the MQSCO structure or the mqclient.ini file to reduce the certificate validation level to `ANY`.
106	The endpoint certificate revocation status is unknown.	Ensure that the CRL or OCSP server that is specified in your HTTP server’s certificate is valid and can be reached from the client host. If certificate revocation checks are not required, you can disable them by using the MQSCO HTTPSCertRevocation field or the HTTPSCertRevocation attribute in the mqclient.ini file.
107	There was a problem with the HTTPS keystore.	See additional information in the message to diagnose and correct the failure.
108	The HTTPS keystore stash file is not accessible.	The HTTPSKeyStore must be accompanied by a stash file (with an extension of .sth) in the same directory, with the same name as the keystore file. Ensure that the stash file exists and is accessible (has `read` permission) to the user ID that is running the IBM MQ client application.