The fields of the WebServer class are listed below. For a complete list of WebServer class members, see the WebServer Members topic.
Public Static Fields
  ACCEPT_NOT_ALLOWED | The resource identified by the request is only capable of generating response entities which have content characteristics not acceptable according to the accept headers sent in the request. Unless it was a HEAD request, the response SHOULD include an entity containing a list of available entity characteristics and location(s) from which the user or user agent can choose the one most appropriate. The entity format is specified by the media type given in the Content-Type header field. Depending upon the format and the capabilities of the user agent, selection of the most appropriate choice MAY be performed automatically. However, this specification does not define any standard for such automatic selection. |
| BAD_GATEWAY | The server, while acting as a gateway or proxy, received an invalid response from the upstream server it accessed in attempting to fulfill the request. |
| BAD_REQUEST | The request could not be understood by the server due to malformed syntax. The client SHOULD NOT repeat the request without modifications. |
| CANNOT_SATISFY_REQUEST_RANGE | A server SHOULD return a response with this status code if a request included a Range request-header field, and none of the range-specifier values in this field overlap the current extent of the selected resource, and the request did not include an If-Range request-header field. (For byte-ranges, this means that the first- byte-pos of all of the byte-range-spec values were greater than the current length of the selected resource.) |
| CONTINUE | The server responds to a partial request and accepts the partial request, telling the client to continue with its request body. |
| dateFormat_ANSI | |
| dateFormat_RFC822 | |
| dateFormat_RFC850 | |
| EXPECTATION_FAILED | The expectation given in an Expect request-header field could not be met by this server, or, if the server is a proxy, the server has unambiguous evidence that the request could not be met by the next-hop server. |
| FORBIDDEN | The server understood the request, but is refusing to fulfill it. Authorization will not help and the request SHOULD NOT be repeated. If the request method was not HEAD and the server wishes to make public why the request has not been fulfilled, it SHOULD describe the reason for the refusal in the entity. If the server does not wish to make this information available to the client, the status code 404 (Not Found) can be used instead. |
| GATEWAY_TIMEOUT | The server, while acting as a gateway or proxy, did not receive a timely response from the upstream server specified by the URI (e.g. HTTP, FTP, LDAP) or some other auxiliary server (e.g. DNS) it needed to access in attempting to complete the request. |
| GONE | The requested resource is no longer available at the server and no forwarding address is known. This condition is expected to be considered permanent. Clients with link editing capabilities SHOULD delete references to the Request-URI after user approval. If the server does not know, or has no facility to determine, whether or not the condition is permanent, the status code 404 (Not Found) SHOULD be used instead. This response is cacheable unless indicated otherwise. The 410 response is primarily intended to assist the task of web maintenance by notifying the recipient that the resource is intentionally unavailable and that the server owners desire that remote links to that resource be removed. Such an event is common for limited-time, promotional services and for resources belonging to individuals no longer working at the server's site. 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 server owner. |
| LENGTH_REQUIRED | The server refuses to accept the request without a defined Content- Length. The client MAY repeat the request if it adds a valid Content-Length header field containing the length of the message-body in the request message. |
| MOVED | The requested resource resides temporarily under a different URI. Since the redirection might be altered on occasion, the client SHOULD continue to use the Request-URI for future requests. This response is only cacheable if indicated by a Cache-Control or Expires header field. |
| MOVED_PERMANENTLY | The requested resource has been assigned a new permanent URI and any future references to this resource SHOULD use one of the returned URIs. Clients with link editing capabilities ought to automatically re-link references to the Request-URI to one or more of the new references returned by the server, where possible. This response is cacheable unless indicated otherwise. |
| NO_CONTENT | The server has fulfilled the request but does not need to return an entity-body, and might want to return updated metainformation. The response MAY include new or updated metainformation in the form of entity-headers, which if present SHOULD be associated with the requested variant. |
| NOT_IMPLEMENTED | The server does not support the functionality required to fulfill the request. This is the appropriate response when the server does not recognize the request method and is not capable of supporting it for any resource. |
| NOT_MODIFIED | If the client has performed a conditional GET request and access is allowed, but the document has not been modified, the server SHOULD respond with this status code. The 304 response MUST NOT contain a message-body, and thus is always terminated by the first empty line after the header fields. |
| POST_MIME_TYPE | |
| PRECONDITION_FAILED | The precondition given in one or more of the request-header fields evaluated to false when it was tested on the server. This response code allows the client to place preconditions on the current resource metainformation (header field data) and thus prevent the requested method from being applied to a resource other than the one intended. |
| PROXY_AUTHENTICATION_REQUIRED | This code is similar to 401 (Unauthorized), but indicates that the client must first authenticate itself with the proxy. The proxy MUST return a Proxy-Authenticate header field containing a challenge applicable to the proxy for the requested resource. The client MAY repeat the request with a suitable Proxy-Authorization header field |
| PUT_NOT_ALLOWED | The method specified in the Request-Line is not allowed for the resource identified by the Request-URI. The response MUST include an Allow header containing a list of valid methods for the requested resource. |
| REQUEST_CONFLICT | The request could not be completed due to a conflict with the current state of the resource. This code is only allowed in situations where it is expected that the user might be able to resolve the conflict and resubmit the request. The response body SHOULD include enough information for the user to recognize the source of the conflict. Ideally, the response entity would include enough information for the user or user agent to fix the problem; however, that might not be possible and is not required. |
| REQUEST_ENTITY_TOO_LARGE | The server is refusing to process a request because the request entity is larger than the server is willing or able to process. The server MAY close the connection to prevent the client from continuing the request. |
| REQUEST_TIMED_OUT | The client did not produce a request within the time that the server was prepared to wait. The client MAY repeat the request without modifications at any later time. |
| REQUEST_URI_TOO_LONG | The server is refusing to service the request because the Request-URI is longer than the server is willing to interpret. This rare condition is only likely to occur when a client has improperly converted a POST request to a GET request with long query information, 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 server is under attack by a client attempting to exploit security holes present in some servers using fixed-length buffers for reading or manipulating the Request-URI. |
| RESET_CONTENT | The server has fulfilled the request and the user agent SHOULD reset the document view which caused the request to be sent. This response is primarily intended to allow input for actions to take place via user input, followed by a clearing of the form in which the input is given so that the user can easily initiate another input action. The response MUST NOT include an entity. |
| SERVER_ERROR | The server encountered an unexpected condition which prevented it from fulfilling the request. |
| SERVICE_UNAVAILABLE | The server is currently unable to handle the request due to a temporary overloading or maintenance of the server. The implication is that this is a temporary condition which will be alleviated after some delay. If known, the length of the delay MAY be indicated in a Retry-After header. If no Retry-After is given, the client SHOULD handle the response as it would for a 500 response. |
| TEMPORARY_REDIRECT | The requested resource resides temporarily under a different URI. Since the redirection MAY be altered on occasion, the client SHOULD continue to use the Request-URI for future requests. This response is only cacheable if indicated by a Cache-Control or Expires header field. |
| UNAUTHORIZED | The request requires user authentication. The response MUST include a WWW-Authenticate header field containing a challenge applicable to the requested resource. The client MAY repeat the request with a suitable Authorization header field. If the request already included Authorization credentials, then the 401 response indicates that authorization has been refused for those credentials. If the 401 response contains the same challenge as the prior response, and the user agent has already attempted authentication at least once, then the user SHOULD be presented the entity that was given in the response, since that entity might include relevant diagnostic information. |
| UNSUPPORTED_MEDIA_TYPE | The server is refusing to service the request because the entity of the request is in a format not supported by the requested resource for the requested method. |
| URL_NOT_FOUND | The server has not found anything matching the Request-URI. No indication is given of whether the condition is temporary or permanent. The 410 (Gone) status code SHOULD be used if the server knows, through some internally configurable mechanism, that an old resource is permanently unavailable and has no forwarding address. This status code is commonly used when the server does not wish to reveal exactly why the request has been refused, or when no other response is applicable. |
| USE_GET | The response to the request can be found under a different URI and SHOULD be retrieved using a GET method on that resource. This method exists primarily to allow the output of a POST-activated script to redirect the user agent to a selected resource. The new URI is not a substitute reference for the originally requested resource. The 303 response MUST NOT be cached, but the response to the second (redirected) request might be cacheable. |
| USE_PROXY | The requested resource MUST be accessed through the proxy given by the Location field. The Location field gives the URI of the proxy. The recipient is expected to repeat this single request via the proxy. 305 responses MUST only be generated by origin servers. |
| VERSION_NOT_SUPPORTED | The server does not support, or refuses to support, the HTTP protocol version that was used in the request message. The server is indicating that it is unable or unwilling to complete the request using the same major version as the client, as described in section 3.1, other than with this error message. The response SHOULD contain an entity describing why that version is not supported and what other protocols are supported by that server. |
| VERSION_STR |
Protected Static Fields
Public Instance Fields
Protected Instance Fields
 agent_id (inherited from Agent) | This is where the agent_id is cached for use by the toString method. |
| agentControllerObj (inherited from Agent) | This is a reference to the AgentController assigned to this agent. |
| authenticationAgent | |
| debugReporter (inherited from Agent) | This is a reference to the Reporter assigned to this agent for debug output. If this field is null (Nothing in Visual Basic) the debug method will be ignored. |
| errorReporter (inherited from Agent) | This is a reference to the Reporter assigned to this agent for error output. If this field is null, (Nothing in Visual Basic), the error methods will be ignored. |
| indexAgent | |
| logger | |
| multihome | |
| ntlmProcessToken | |
| ntlmProcessUser | |
| numConnections | |
| printlnReporter (inherited from Agent) | This is a reference to the Reporter assigned to this agent for println output. If this field is null (Nothing in Visual Basic) the println method will be ignored. |
| proxyAgent | |
| redirectAgent | |
| refuseRequests | |
| runThread | |
| secureSocket | |
| threadPool | |
| warningReporter (inherited from Agent) | This is a reference to the Reporter assigned to this agent for warning output. If this field is null (Nothing in Visual Basic) the warning methods will be ignored. |
See Also
WebServer Class | com.neokernel.httpd Namespace