Abstract: Techniques for redirecting a client request. The client request is received at a first server. The first server forwards the client request to a second server. The first server receives a result message from the second server. The first server identifies, in the result message, references to resources of the second server. The first server replaces, in the result message, all references to resources of the second server with translated references that reference the first server without replacing references to resources of any other entity other than the second server. The first server sends the translated references to the client as a response to the client request.

Abstract: A method of redirecting a client request, directed from a client to a first server, to a second server. The client request is received at the second server and automatically forwarded or redirected to the first server. The first server processes the request and generates a result message, which may include a document formatted in a markup language. The first server sends the result message to the second server. A process at the second server identifies, in the result message, references to resources of the first server. The references to resources of the first server are replaced with translated references that reference the second server, and the translated references are sent to the client as a response to the client request. As a result, subsequent client requests that are based on the response or the result message are always directed to the second server rather than to the first server. Accordingly, the second server can prevent the client from communicating directly with the first server.

Abstract: A method of redirecting a client request received by a second server to a first server. The client request requires use of a Secure Sockets Layer (SSL) capability. The client request is received at the second serve and automatically forwarded or redirected to the first server, The first server processes the request and generates a result message. The first server sends the result message to the second server. A process at the second server identifies, in the, result message, reference to resources of the first server. The references to resources of the first server are replaced with translated references that reference the second server, and the translated references are sent to the client as a response to the client request. Subsequent client requests that are based on the, response or the result message are always directed to the second server rather than to the first server.

Abstract: A method and apparatus that provide network access control are disclosed. In one embodiment, a network access control apparatus is configured to receive and authenticate a password that uses the “Fortezza” cryptographic protocol, and to receive and authenticate passwords of other types, to thereby selectively permit a client associated with the Fortezza password to access a protected network. A Fortezza card reader is coupled to the client and associated with a Fortezza card that contains the Fortezza password. A network access server is logically coupled to the client. An access control server is coupled logically between the client and the protected network and that controls access of the client to the protected network. A Fortezza authentication server is coupled to the access control server for communication therewith. A database is coupled to the access control server and that contains profile information associated with the user.

Abstract: A method and apparatus for notifying a first network node that a second network node has gone off-line during a communication session is disclosed. The first network node may be a client and the second network node may be a server. The client and the server communicate using an embedded protocol, such as telnet. The protocol defines a login process that must be used by the client to establish a logical connection to the server. The protocol also specifies that the server must immediately issue a response to a login attempt, by either establishing a connection or issuing an error message. The first network node determines that no communications have been received from the second server in a pre-determined period of time. The first network node generates invalid login information, such as a randomly generated invalid user id and an invalid password. A login command is sent from the first network node to the second network node. The login command includes the previously generated invalid login information.