Page not found
This page is no longer on
this server.
Please go here and try again
Or were you looking for:
Rushes
Florist Online Flowers
Tekram
Properties Commercial Property
Aqualoc Plumbed
in Water Coolers
Crown
Water and Coffee Coffee
and water Vending Company
More Clients
Or it could be one of the errors below:
0 = No Connect or response
200 = OK
201 = Created The request has been fulfilled and resulted
in a new resource being created. The newly created resource can be
referenced
by the URL(s) returned in the entity of the response, with the most
specific URL for the resource given by a Location header field. The
origin server MUST create the resource before returning the 201 status
code. If the action cannot be carried out immediately, the server
should respond with 202 (Accepted) response instead.
202 = Accepted The request has
been accepted for processing, but the processing has not been completed.
The
request MAY or MAY NOT eventually be acted upon, as it MAY be
disallowed when processing actually takes place. There is no
facility for re-sending a status code from an asynchronous operation
such as this.
The 202 response is intentionally non-committal. Its purpose is
to allow a server to accept a request for some other process (perhaps
a batch-oriented process that is only run once per day) without
requiring that the user agent's connection to the server persist
until the process is completed. The entity returned with this response
SHOULD include an indication of the request's current status and
either a pointer to a status monitor or some estimate of when the
user can expect the request to be fulfilled.
204 = No Content The server has fulfilled the request but
there is no new information to send back. If the client is a user
agent,
it SHOULD NOT change its document view from that which caused
the request to be sent. This response is primarily intended to
allow input for actions to take place without causing a change
to the user agent's active document view. The response MAY include
new metainformation in the form of entity-headers, which SHOULD
apply to the document currently in the user agent's active view.
back to top
301 = Moved Permanently The requested resource has been
assigned a new permanent URI and any future references to this resource
SHOULD be done using one of the returned URIs. Clients with link
editing capabilities SHOULD 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 cachable unless
indicated otherwise.
If the new URI is a location, its URL SHOULD be given by the Location
field in the response. Unless the request method was HEAD, the
entity of the response SHOULD contain a short hypertext note with
a hyperlink to the new URI(s).
If the 301 status code is received in response to a request other
than GET or HEAD, the user agent MUST NOT automatically redirect
the request unless it can be confirmed by the user, since this
might change the conditions under which the request was issued.
Note: When automatically redirecting a POST request after receiving
a 301 status code, some existing HTTP/1.0 user agents will erroneously
change it into a GET request.
302 = Moved Temporarily 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 cachable if indicated
by a Cache-Control or Expires header field.
If the new URI is a location, its URL SHOULD be given by the
Location field in the response. Unless the request method was
HEAD, the entity of the response SHOULD contain a short hypertext
note with a hyperlink to the new URI(s).
If the 302 status code is received in response to a request
other than GET or HEAD, the user agent MUST NOT automatically
redirect the request unless it can be confirmed by the user,
since this might change the conditions under which the request
was issued.
Note: When automatically redirecting a POST request after receiving
a 302 status code, some existing HTTP/1.0 user agents will erroneously
change it into a GET request.
304 = 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
response MUST NOT contain a message-body.
The response MUST include the following header fields:
Date
ETag and/or Content-Location, if the header would have been
sent in a 200 response to the same request
Expires, Cache-Control, and/or Vary, if the field-value might
differ from that sent in any previous response for the same
variant
If the conditional GET used a strong cache validator, the response
SHOULD NOT include other entity-headers.
Otherwise (i.e., the conditional GET used a weak validator),
the response MUST NOT include other entity-headers; this prevents
inconsistencies between cached entity-bodies and updated headers.
If a 304 response indicates an entity not currently cached,
then the cache MUST disregard the response and repeat the request
without the conditional.
If a cache uses a received 304 response to update a cache
entry, the cache MUST update the entry to reflect any new field
values given in the response.
The 304 response MUST NOT include a message-body, and thus
is always terminated by the first empty line after the header
fields. back to top
400 = Bad Request The request could not be understood by
the server due to malformed syntax. The client SHOULD NOT repeat
the request
without modifications.
401 = 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 MAY include relevant diagnostic information.
403 = 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.
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.
404 = Not Found The server has not found anything matching
the Request-URI. No indication is given of whether the condition
is temporary
or permanent.
If the server does not wish to make this information available
to the client, the status code 403 (Forbidden) can be used instead.
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. back
to top
500 = Internal Server Error The server encountered an unexpected
condition, which prevented it from fulfilling the request.
501 = 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.
502 = 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.
503 = 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.
Note: The existence of the 503 status code does not imply that
a server must use it when becoming overloaded. Some servers may
wish to simply refuse the connection.
504 = No Service
back to top
|