Responses To Server Challenges Included In A Hypertext Transfer Protocol Header
AssigneeHewlett Packard Enterprise Development LP
InventorMike Beiter
Life of this patent
Estimating the term…
Abstract
Example embodiments relate to verification of client requests based on a response to a challenge (135; 235) included in an HTTP Header. In some embodiments, a server computing device (100; 300; 350) may generate a challenge (130; 230) in response to receipt of a request from a client (200; 330; 380) and may include a random nonce with the challenge. In some embodiments, the server computing device (100; 300; 350) may then verify that a second request includes, in an HTTP header, a response to the challenge (135; 235) that corresponds to the random nonce. Additional example embodiments relate to transmission of a response to a challenge from a client computing device (200; 330; 380) to the server (100; 300; 350).
Claims13
1-15. (canceled)
A server computing device comprising:
- a processor to:
- generate a challenge in response to receipt of a first request from a client, wherein the challenge includes a random nonce in a Hypertext Transfer Protocol (HTTP) header,
- initiate transmission of the challenge to the client in response to the first client request,
- receive a second request from the client, and
- verify, based on examination of data included in an HTTP header of the second request, that the second request includes a response to the challenge that is identical to the random nonce.
A non-transitory machine-readable storage medium encoded with instructions executable by a processor of a client computing device, the machine-readable storage medium comprising:
- instructions for receiving, in response to a first request sent to a server, a challenge generated by the server, wherein the challenge includes a random nonce in an HTTP header of a response from the server;
- instructions for performing a transformation operation to modify a transport representation of the random nonce, the transformation operation comprising reading the random nonce from the HTTP header of the response and inserting a value identical to the random nonce into an HTTP header of a next request;
- and
- instructions for transmitting, to the server, the modified representation of the random nonce in the HTTP header of the next request.
A method comprising:
- generating, in a server computing device, a challenge in response to receipt of a first request from a client, wherein the challenge includes a random nonce;
- transmitting the challenge to the client in response to receipt of the first request, wherein the random nonce is included in an HTTP header of a response to the first request;
- receiving a second request from the client;
- determining whether the client has authenticated the second request by determining whether the client has inserted a response to the challenge that is identical to the random nonce in an HTTP header of the second request:
- and
- ignoring the second request when it is determined that the client has not authenticated the second request.
Dependencies are inferred from the claim text.