![]() Instead of using Service Unavailable: This is typically sent when the OCS is being over encumbered. If this is the case, the client will most likely FIN or RST the TCP socket. A 407 cannot be sent to a client while using WSA as transparent proxy, as the client does not know the proxy exists. This is sent only if the request was sent explicitly to the proxy. Typically, the server will include some sort of description of the cause within the HTTP data (HTML response).Ĥ04 Not Found: The requested object does not exist on the server.Ĥ07 Proxy Authentication Required: This is the same as a 401, except that it is specifically for authentication to a proxy, not the OCS. There are many causes for why a server may deny access to an object. The available methods of authentication are specified in a 403 Forbidden: The client is denied from accessing the requested object. This is because the appliance is spoofing itself as if it were the OCS (origin content server). When using the Cisco Web Security appliance (WSA) in transparent mode, a 401 is sent back to the client when authentication is enabled on the proxy. The 401 is used for authentication to a destination web server. RFC 2616 should be referenced for proper syntax.Ĥ01 Unauthorized: The object requested requires authentication in order to be accessed. Possible causes could be due to multiple headers being on the same line, spaces in a header, no HTTP/1.1 in the URI, so forth. If further details are discovered, this article can be updated.Ĥ00 Bad Request: This means the something in the HTTP request is not following correct syntax. If the object has not changed since the fetched date, the server will send back a 304 Not Modified response.ģ07 Temporary Redirect: For all intents and purposes, it has the same meaning as the 302. If the object has been modified since that date, the server will respond with a 200 OK and a fresh copy of the object. ![]() This header tells the server that the client has a copy of the requested object in it's local cache and included is the date the object was fetched. This is literally a standard HTTP GET that includes the header If-modified-since. ![]() The client is instructed to make a new request for the object specified in the Location: header.ģ04 Not Modified: This is in response to a GIMS (GET If-modified-since). This signifies that the request is successful without any problems.ģ02 Found: This is a temporary redirection. When it is done scanning the first set of bytes and did not detect a virus, it will send a 100 Continue to let the client know to send the rest of the object.Ģ00 OK: The most common response code. ![]() In regards to ICAP services (such as virus scanning), the server may only want to see first x amount of bytes. This is an informational response that let's the client know that it can continue to send data. Response codes indicate the reasons behind successful and failed HTTP requests.įor full detailed information regarding HTTP response codes, please see RFC 2616 (HTTP), section 10.īelow are details regarding the most common response code that you are likely to run into:ġ00 Continue: Typically seen in regards to the ICAP protocol. ![]() The server responses are classified by a numerical response code. HTTP always has a client request and a server response. What do the different HTTP response codes mean?Įnvironment: Cisco Web Security appliance (WSA) running any AsyncOS version ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |