Website server request rerouting

1. A method, comprising:

receiving, from a client device, an initial website request to access a website;

in response to receiving the initial website request to access the website, dynamically trapping the initial website request in an inspection stage and determining whether the website is in an active state or a dormant state;

in response to determining that the website is in the dormant state, converting the website from the dormant state to the active state;

moving the initial website request to a processing stage when the website is in the active state;

establishing a website session with the client device;

receiving a subsequent website request to access the website from the client device within the website session; and

responsive to receiving the subsequent website request, moving the subsequent website request to the processing stage by bypassing the inspection stage and skipping determining whether the website is in the active state or the dormant state.

2. The method of claim 1 , further comprising:

requesting a website presentation state for the website, the website presentation state being one of a plurality of states including the active state and the dormant state.

3. The method of claim 1 , further comprising:

holding the initial website request in a request queue while the initial website request is in the inspection stage; and

accessing the initial website request from the request queue.

4. The method of claim 1 , further comprising:

inspecting a security certificate associated with the initial website request before the initial website request is placed in the inspection stage.

5. The method of claim 1 , wherein the initial website request is a secure client request, the method further comprising:

routing the secure client request through a secure sockets layer channel.

6. The method of claim 1 , further comprising:

formulating a loading plan for loading the website in the dormant state in response to the initial website request; and

loading the website in the dormant state from a dormant website storage according to the loading plan.

7. The method of claim 1 , further comprising:

formulating a configuration plan for configuring the website in response to the initial website request; and

configuring the website according to the configuration plan.

8. The method of claim 1 , further comprising:

configuring the website session based at least on the initial website request to process additional website requests.

9. The method of claim 1 , wherein converting the website from the dormant state to the active state comprises:

retrieving at least a portion of the website from a dormant website storage.

10. A system, comprising:

one or more hardware processors; and

at least one computer readable storage medium including instructions which, when executed by the one or more hardware processors, cause the one or more hardware processors to:

detect an initial website request from a client device to access a website, the initial website request being dynamically trapped in an inspection stage when the initial website request is received;

determine whether the website is in an active state or a dormant state in response to detecting the initial website request in the inspection stage;

convert the website from the dormant state to the active state in response to determining that the website is in the dormant state;

route the initial website request to the website when the website is in the active state;

establish a website session with the client device;

detect an additional website request to access the website from the client device within the website session; and

responsive to detecting the additional website request, route the additional website request to the website by bypassing the inspection stage and skipping determining whether the website is in the active state or the dormant state.

11. The system of claim 10 , wherein the initial website request is a secure client request and the instructions, when executed by the one or more hardware processors, cause the one or more hardware processors to:

route the secure client request through a secure sockets layer channel.

12. The system of claim 10 , wherein the instructions, when executed by the one or more hardware processors, cause the one or more hardware processors to:

hold the initial website request in a request queue; and

access the initial website request from the request queue.

13. The system of claim 10 , wherein the instructions, when executed by the one or more hardware processors, cause the one or more hardware processors to:

retire the website as a dormant website to be stored in a dormant website storage when the website is not accessed for at least a dormancy period.

14. The system of claim 10 , wherein the instructions, when executed by the one or more hardware processors, cause the one or more hardware processors to:

load the website in the dormant state on an ad hoc basis based at least on the initial website request.

15. The system of claim 10 , wherein the instructions, when executed by the one or more hardware processors, cause the one or more hardware processors to:

formulate a configuration plan for configuring the website based at least on the initial website request; and

configure the website according to the configuration plan.

16. The system of claim 10 , wherein the instructions, when executed by the one or more hardware processors, cause the one or more hardware processors to:

direct the initial website request to an application of the website based at least on the initial website request.

17. The system of claim 10 , wherein the instructions, when executed by the one or more hardware processors, cause the one or more hardware processors to:

retrieve at least a portion of the website from a dormant website storage.

18. A website server, comprising:

a storage having stored therein a website that has not been active for at least a dormancy period;

a hardware communication interface configured to receive an initial website request to access the website from a client device and to receive a subsequent website request to access the website from the client device; and

at least one hardware processor configured via computer-readable instructions to:

in response to receiving the initial website request, dynamically trap the initial website request in an inspection stage and determine whether the website is in a dormant state or an active state;

in response to determining that the website is in the dormant state, convert the website from the dormant state to the active state;

route the initial website request to the website when the website is in the active state;

establish a website session with the client device; and

in response to receiving the subsequent website request to access the website from the client device within the website session, route the subsequent website request to the website by bypassing the inspection stage and skipping determining whether the website is in the active state or the dormant state.

19. The website server of claim 18 , further comprising:

a request queue that holds the initial website request in the inspection stage.

20. The website server of claim 18 , wherein the at least one hardware processor is further configured via the computer-readable instructions to:

retire an active website that has not been accessed for at least the dormancy period into a dormant website stored in the storage.