The Test Participant Connection feature allows you to
test the gateway or Web server. If you are the Community Manager,
you can also select a specific participant. The test consists of
sending a blank POST request to a gateway or URL. The request is
similar to entering the Yahoo's URL (www.yahoo.com) into
your browser address field. Nothing is sent; it is an empty request.
The response received from the gateway or Web server will indicate
its status:
- If a response is returned, the server is up.
- If nothing is returned, the server is down.
Important:
The Test Participant Connection feature works with HTTP
that does not require any connection parameters.
To test a participant connection:
- Click Tools > Test Participant Connection.
The system displays the Test Participant Connection screen.
- Select the test criteria from the drop-down lists.
Table 35. Test Participant Connection Values
Value |
Description |
Participant |
Participant to be tested (Community Manager
only). |
Gateway |
Displays available gateways based on the participant
selected above. |
URL |
Dynamically populated based on the Gateway
selected above. |
Command |
Post or Get. |
- Click Test URL. The system displays the
test results. For information on the status code returned, see the
following sections.
200 Series:
- 200 - OK - Successful transmission. This is not an error. Here
is the file that you requested.
- 201 - Created - The request has been fulfilled and resulted
in the creation of a new resource. The newly created resource can
be referenced by the URLs returned in the URL-header field of the
response, with the most specific URL for the resource given by a
Location header field.
- 202 - Accepted - The request has been accepted for processing,
but the processing has not yet completed.
- 203 - Non-Authoritative Information - The returned META information
in the Entity-Header is not the definitive set as available from
the origin server, but is gathered from a local or third-party copy.
- 204 - No Content - The server has fulfilled the request, but
there is no new information to send back.
- 206 - Partial Content - You requested a range of bytes in the
file, and here they are. This is new in HTTP 1.1
300 Series:
- 301 - Moved Permanently - The requested resource has been assigned
a new permanent URL and any future references to this resource should
be done using one of the returned URLs.
- 302 - Moved Temporarily - The requested resource resides temporarily
under a new URL. Redirection to a new URL. The original page has
moved. This is not an error; most browsers invisibly fetch the new
page when they see this result.
400 Series:
- 400 - Bad Request - The request could not be understood by the
server because it has a malformed syntax. Bad request was made by
the client.
- 401 - Unauthorized - The request requires user authentication.
The response must include a WWW-Authenticate header field containing
a challenge applicable to the requested source. The user asked for
a document but did not provide a valid username or password.
- 402 - Payment Required - This code is not currently supported,
but is reserved for future use.
- 403 - Forbidden - The server understood the request but is refusing
to perform the request because of an unspecified reason. Access
is explicitly denied to this document. (This might happen because
the web server doesn't have read permission for the file you're
requesting.) The server refuses to send you this file. Maybe permission
has been explicitly turned off.
- 404 - Not Found - The server has not found anything matching
the requested URL. This file doesn't exist. What you get if you
give a bad URL to your browser. This can also be sent if the server
has been told to protect the document by telling unauthorized people
that it doesn't exist. 404 errors are the result of requests for pages
which do not exist, and can come from a URL typed incorrectly, a bookmark
which points to a file no longer there, search engines looking for
a robots.txt (which is used to mark pages you don't want indexed
by search engines), people guessing filenames, bad links from your
site or other sites, etc.
- 405 - Method Not Allowed - The method specified in the request
line is not allowed for the resource identified by the request URL.
- 406 - None Acceptable - The server has found a resource matching
the request URL, but not one that satisfies the conditions identified
by the Accept and Accept-Encoding request headers.
- 407 - Proxy Authentication Required - This code is reserved
for future use. It is similar to 401 (Unauthorized) but indicates
that the client must first authenticate itself with a proxy. HTTP
1.0 does not provide a means for proxy authentication.
- 408 - Request Time out - The client did not produce a request
within the time the server was prepared to wait.
- 409 - Conflict - The request could not be completed due to a
conflict with the current state of the resource.
- 410 - Gone - The requested resource is no longer available at
the server and no forwarding address is known.
- 411 - Authorization Refused - The request credentials provided
by the client were rejected by the server or insufficient to grant
authorization to access the resource.
- 412 - Precondition Failed
- 413 - Request Entity Too Large
- 414 - Request URI Too Large
- 415 - Unsupported Media Type
500 Series:
- 500 - Internal Server Error - The server encountered an unexpected
condition that prevented it from filling the request. Something
went wrong with the web server and it couldn't give you a meaningful
response. There is usually nothing that can be done from the browser
end to fix this error; the server administrator will probably need
to check the server's error log to see what happened. This is often the
error message for a CGI script which has not been properly coded.
- 501 - Method Not Implemented - The server does not support the
functionality required to fulfill the request. Application method
(either GET or POST) is not implemented.
- 502 - Bad Gateway - The server received an invalid response
from the gateway or upstream server it accessed in attempting to
fulfill the request.
- 503 - Service Temporarily Unavailable - The server is currently
unable to handle the request due to a temporary overloading or maintenance
of the server. Server is out of resources.
- 504 - Gateway Time out - The server did not receive a timely
response from the gateway or upstream server it accessed in attempting
to complete the request.
- 505 - HTTP Version Not Supported
