Stateless web elements that decode or decrypt data
AssigneeCapital One Services, LLC
InventorsErol Unal, Jason Vanderslice, Mark Morrison, Preetha Veeraraghavan
Life of this patent
Estimating the term…
Abstract
In some implementations, a user device may receive, from a web host, code associated with a webpage. The user device may perform, using a host application, at least one call to an application programming interface (API) function on behalf of a stateless web element in the webpage. The user device may receive, in response to the at least one call to the API function, encoded data. The user device may pass the encoded data to a stateless web element for decoding. The user device may output a rendered webpage with the stateless web element including a decoded version of the encoded data.
Claims20
A system for using stateless web elements, the system comprising:
- one or more memories;
- and
- one or more processors, communicatively coupled to the one or more memories, configured to:
- receive, from a web host, code associated with a webpage;
- perform a handshake between a stateless web element in the webpage and an application programming interface (API) function in order to establish a shared secret;
- perform, using a host application, at least one call to the API function on behalf of the stateless web element;
- receive, in response to the at least one call, encrypted data;
- pass the encrypted data to the stateless web element for decryption using the shared secret;
- perform an additional handshake between an additional stateless web element in the webpage and an additional API function in order to establish an additional shared secret;
- perform, using the host application, at least one additional call to the additional API function on behalf of the additional stateless web element;
- receive, in response to the at least one additional call, additional encrypted data;
- pass the additional encrypted data to the additional stateless web element for decryption using the additional shared secret;
- and
- output a rendered webpage with the stateless web element including a decrypted version of the encrypted data,
- wherein the rendered webpage further includes the additional stateless web element with a decrypted version of the additional encrypted data.
A method of using stateless web elements, comprising:
- receiving, from a user device and at a web server, a request to access a webpage;
- performing, using a host application executed by the web server, at least one call to an application programming interface (API) function on behalf of a stateless web element in the webpage;
- receiving, at the host application and in response to the at least one call to the API function, encoded data;
- passing the encoded data from the host application to the stateless web element for decoding;
- rendering, by the web server, the webpage with the stateless web element including a decoded version of the encoded data;
- performing, using the host application, at least one additional call to an additional API function on behalf of an additional stateless web element;
- receiving, in response to the at least one additional call, additional encoded data;
- passing the additional encoded data to the additional stateless web element for decoding;
- and
- transmitting, to the user device, instructions for a rendered version of the webpage,
- wherein the rendered version of the webpage includes the additional stateless web element with a decoded version of the additional encoded data.
A non-transitory computer-readable medium storing a set of instructions for using stateless web elements, the set of instructions comprising:
- one or more instructions that, when executed by one or more processors of a device, cause the device to:
- receive, from a web host, code associated with a webpage;
- perform, using a host application, at least one call to an application programming interface (API) function on behalf of a stateless web element in the webpage;
- receive, in response to the at least one call to the API function, encoded data;
- pass the encoded data to the stateless web element for decoding;
- perform, using the host application, at least one additional call to an additional API function on behalf of an additional stateless web element;
- receive, in response to the at least one additional call, additional encoded data;
- pass the additional encoded data to the additional stateless web element for decoding;
- and
- output a rendered webpage with the stateless web element including a decoded version of the encoded data,
- wherein the rendered webpage further includes the additional stateless web element with a decoded version of the additional encoded data.
Dependencies are inferred from the claim text.