Problems with the HTTP Connection Handler
When problems with the HTTP Connection Handler occur, first look at the HTTP connection handler log to diagnose the issue.
The following HTTP log examples detail various errors that can occur related to the HTTP Connection Handler:
- Failed request due to a non-existent resource
-
The server receives a status code 404, which indicates the server could not match the URI:
[15/Mar/2012:17:39:39 -0500] RESULT requestID=0 from="10.2.1.113:52958" method="GET" url="https://10.2.1.113:443/Aleph/Users/uid=user.1,ou=people, dc=example,dc=com" requestHeader="Host: x2270-11.example.lab" requestHeader="Accept: / " requestHeader="User-Agent: curl/7.21.6 (i386-pc-centos2.10) libcurl/7.21.6 OpenSSL/1.0.0d zlib/1.2.5 libidn/1.22 libssh2/1.2.7" authorizationType="Basic" statusCode=404 etime=81.484 responseContentLength=103 responseHeader="Access-Control-Allow-Credentials:true" responseContentType="application/json"
- Failed request due to a malformed request body
-
The server receives a status code 400, which indicates that the request had malformed syntax in its request body:
[15/Mar/2012:17:47:23-0500] RESULT requestID=10 from="10.2.1.113:55284" method="POST" url="https://10.2.1.113:443/Aleph/Users" requestHeader="Host: x2270-11.example.lab" requestHeader="Expect: 100-continue" requestHeader="Accept: / " requestHeader="Content-Type: application/json" requestHeader="User-Agent: curl/ 7.21.6 (i386-pc-centos2.10) libcurl/7.21.6 OpenSSL/1.0.0d zlib/1.2.5 libidn/1.22 libssh2/1.2.7" authorizationType="Basic" requestContentType="application/json" requestContentLength=5564 statusCode=400 etime=15.272 responseContentLength=133 responseContentType="application/json"
- Failed request due to an unsupported HTTP method
-
The server receives a status code 405, which indicates that the specified HTTP method (e.g.,
"PATCH") in the request line is not allowed for the resource identified in the URI:
[15/Mar/2012:17:48:59-0500] RESULT requestID=11 from="10.2.1.113:55763" method="PATCH" url="https://10.2.1.113:443/Aleph/Users" requestHeader="Host: x2270-11.example.lab" requestHeader="Accept: / " requestHeader="Content-Type: application/json" requestHeader="User-Agent: curl/7.21.6 (i386-pc-centos2.10) libcurl/7.21.6 OpenSSL/1.0.0d zlib/1.2.5 libidn/1.22 libssh2/1.2.7" authorization-Type="Basic" requestContentType="application/json" statusCode=405 etime=6.807 responseContentLength=0 responseHeader="Allow: POST, GET, OPTIONS, HEAD"
- Failed request due to an unsupported media type
-
The server receives a status code 415, which indicates that the request entity is in a format that is not supported by the requested resource:
[15/Mar/2012:17:44:45-0500] RESULT requestID=4 from="10.2.1.113:54493" method="POST" url="https://10.2.1.113:443/Aleph/Users" requestHeader="Host: x2270-11.example.lab" requestHeader="Accept: / " requestHeader="Content-Type: application/atom+xml" requestHeader="User-Agent: curl/7.21.6 (i386-pc-centos2.10) libcurl/7.21.6 OpenSSL/1.0.0d zlib/1.2.5 libidn/1.22 libssh2/1.2.7" authorizationType="Basic" requestContentType="application/atom+xml" requestContentLength=3 statusCode=415 etime=6.222 responseContentLength=1402 responseHeader="Cache-Control: must-revalidate,no-cache,no-store" responseContentType="text/html;charset=ISO-8859-1"
- Failed request due to an authentication error
-
The server receives a status code 401, which indicates that the request requires user authentication:
[15/Mar/2012:17:46:06-0500] RESULT requestID=8 from="10.2.1.113:54899" method="GET" url="https://10.2.1.113:443/Aleph/Schemas" requestHeader="Host: x2270-11.example.lab" requestHeader="Accept: / " requestHeader="User-Agent: curl/7.21.6 (i386-pc-centos2.10) libcurl/7.21.6 OpenSSL/1.0.0d zlib/1.2.5 libidn/1.22 libssh2/ 1.2.7" authorizationType="Basic" statusCode=401 etime=2.751 responseContentLength=63 responseHeader="WWW-Authenticate: Basic realm=SCIM" responseHeader="Access-Control-Allow-Credentials: true" responseContentType="application/json"