Methods and apparatuses for providing internet-based proxy services

1. A method in a proxy server, comprising:

receiving, at the proxy server from a first client network application, a first request for an action to be performed on an identified network resource of a domain of an origin server, wherein the first request is received at the proxy server as a result of a Domain Name System (DNS) request for the domain returning an IP address of the proxy server;

determining that the first request is indicative of being from a first bot;

responsive to the determining that the first request is indicative of being from the first bot, responding to the first request including transmitting a block page to the first client network application that includes a mechanism to allow a human user of the first client network application to provide input that indicates that they are human and not the first bot;

determining that no input is received from the first client network application through the mechanism in the block page that indicates that the first request is not from the first bot; and

responsive to the determining that no input is received from the first client network application through the mechanism in the block page that indicates that the first request is not from the first bot, blocking the first request.

2. The method of claim 1 , further comprising:

receiving, at the proxy server from a second client network application, a second request for an action to be performed on the identified network resource of the domain;

determining that the second request is indicative of being from a second bot;

responsive to the determining that the second request is indicative of being from a second bot, responding to the second request including transmitting the block page to the second client network application, the block page including the mechanism to allow a human user of the second client network application to provide input that indicates that they are not a bot;

receiving, from the second client network application through the mechanism in the block page, input that indicates that the second request is not from the second bot; and

responsive to that received input, transmitting the second request to the origin server.

3. The method of claim 2 , further comprising:

responsive to the received input that indicates that the second request is not from the second bot, setting a cookie such that a subsequent request received from the second client network application that includes that cookie will not be blocked by the proxy server.

4. The method of claim 1 , further comprising:

receiving, at the proxy server, a third request for an action to be performed on the identified network resource;

determining that the third request originates from a search engine or a web crawler, and responsive to this determination, determining that the identified network resource is available in cache; and

responsive to determining that the identified network resource is available in cache, returning the identified network resource from the cache without querying the origin server.

5. The method of claim 1 , wherein determining that the first request is indicative of being from the first bot includes determining that a source IP address of the first request is represented on a restricted list.

6. The method of claim 1 , wherein determining that the first request is indicative of being from the first bot includes analyzing a set of one or more characteristics associated with the request that indicates that the first request is indicative of being from the first bot.

7. The method of claim 6 , wherein the set of one or more characteristics include one or more of whether images are supported, whether JavaScript is supported, a type of client network application making the first request, fonts installed on the client network application making the first request, whether the client network application supports plugins, whether the client network application stores cookies, whether the client network application responds from a same IP address for various protocol requests, or any combination thereof.

8. The method of claim 1 , further comprising:

receiving, at the proxy server from a second client network application, a second request for an action to be performed on the identified network resource of the origin server;

determining that the second request is not indicative of being from a second bot;

responsive to the determining that the second request is not indicative of being from a second bot, transmitting the second request to the origin server.

9. A proxy server, comprising:

a memory to store instructions;

a processor coupled with the memory to process the stored instructions to:

receive, at the proxy server from a first client network application, a first request for an action to be performed on an identified network resource of a domain of an origin server, wherein the first request is to be received at the proxy server as a result of a Domain Name System (DNS) request for the domain returning an IP address of the proxy server;

determine that the first request is indicative of being from a first bot;

responsive to the determination that the first request is indicative of being from the first bot, respond to the first request including transmission of a block page to the first client network application that includes a mechanism to allow a human user of the first client network application to provide input that indicates that they are human and not the first bot;

determine that no input is received from the first client network application through the mechanism in the block page that indicates that the first request is not from the first bot; and

responsive to the determination that no input is received from the first client network application through the mechanism in the block page that indicates that the first request is not from the first bot, block the first request.

10. The proxy server of claim 9 , wherein the processor is further to process the stored instructions to:

receive, at the proxy server from a second client network application, a second request for an action to be performed on the identified network resource of the domain;

determine that the second request is indicative of being from a second bot;

responsive to the determination that the second request is indicative of being from a second bot, respond to the second request including transmission of the block page to the second client network application, the block page including the mechanism to allow a human user of the second client network application to provide input that indicates that they are not a bot;

receive, from the second client network application through the mechanism in the block page, input that indicates that the second request is not from the second bot; and

responsive to that received input, transmit the second request to the origin server.

11. The proxy server of claim 10 , wherein the processor is further to process the stored instructions to:

responsive to the received input that indicates that the second request is not from the second bot, set a cookie such that a subsequent request received from the second client network application that includes that cookie will not be blocked by the proxy server.

12. The proxy server of claim 9 , wherein the processor is further to process the stored instructions to:

receive, at the proxy server, a third request for an action to be performed on the identified network resource;

determine that the third request originates from a search engine or a web crawler, and responsive to this determination, determine that the identified network resource is available in cache; and

responsive to the determination that the identified network resource is available in cache, return the identified network resource from the cache without querying the origin server.

13. The proxy server of claim 9 , wherein the determination that the first request is indicative of being from the first bot includes a determination that a source IP address of the first request is represented on a restricted list.

14. The proxy server of claim 9 , wherein the determination that the first request is indicative of being from the first bot includes the proxy server to analyze a set of one or more characteristics associated with the request that indicates that the first request is indicative of being from the first bot.

15. The proxy server of claim 14 , wherein the set of one or more characteristics include one or more of whether images are supported, whether JavaScript is supported, a type of client network application making the first request, fonts installed on the client network application making the first request, whether the client network application supports plugins, whether the client network application stores cookies, whether the client network application responds from a same IP address for various protocol requests, or any combination thereof.

16. The proxy server of claim 9 , wherein the processor is further to process the stored instructions to:

receive, at the proxy server from a second client network application, a second request for an action to be performed on the identified network resource of the origin server;

determine that the second request is not indicative of being from a second bot;

responsive to the determination that the second request is not indicative of being from a second bot, transmit the second request to the origin server.

17. A non-transitory machine-readable storage medium that provides instructions that, when executed by a processor of a proxy server, cause said processor to perform operations comprising:

receiving, at the proxy server from a first client network application, a first request for an action to be performed on an identified network resource of a domain of an origin server, wherein the first request is received at the proxy server as a result of a Domain Name System (DNS) request for the domain returning an IP address of the proxy server;

determining that the first request is indicative of being from a first bot;

responsive to the determining that the first request is indicative of being from the first bot, responding to the first request including transmitting a block page to the first client network application that includes a mechanism to allow a human user of the first client network application to provide input that indicates that they are human and not the first bot;

determining that no input is received from the first client network application through the mechanism in the block page that indicates that the first request is not from the first bot; and

responsive to the determining that no input is received from the first client network application through the mechanism in the block page that indicates that the first request is not from the first bot, blocking the first request.

18. The non-transitory machine-readable storage medium of claim 17 , wherein the operations further comprise:

receiving, at the proxy server from a second client network application, a second request for an action to be performed on the identified network resource of the domain;

determining that the second request is indicative of being from a second bot;

responsive to the determining that the second request is indicative of being from a second bot, responding to the second request including transmitting the block page to the second client network application, the block page including the mechanism to allow a human user of the second client network application to provide input that indicates that they are not a bot;

receiving, from the second client network application through the mechanism in the block page, input that indicates that the second request is not from the second bot; and

responsive to that received input, transmitting the second request to the origin server.

19. The non-transitory machine-readable storage medium of claim 18 , wherein the operations further comprise:

responsive to the received input that indicates that the second request is not from the second bot, setting a cookie such that a subsequent request received from the second client network application that includes that cookie will not be blocked by the proxy server.

20. The non-transitory machine-readable storage medium of claim 17 , wherein the operations further comprise:

receiving, at the proxy server, a third request for an action to be performed on the identified network resource;

determining that the third request originates from a search engine or a web crawler, and responsive to this determination, determining that the identified network resource is available in cache; and

responsive to determining that the identified network resource is available in cache, returning the identified network resource from the cache without querying the origin server.

21. The non-transitory machine-readable storage medium of claim 17 , wherein determining that the first request is indicative of being from the first bot includes determining that a source IP address of the first request is represented on a restricted list.

22. The non-transitory machine-readable storage medium of claim 17 , wherein determining that the first request is indicative of being from the first bot includes analyzing a set of one or more characteristics associated with the request that indicates that the first request is indicative of being from the first bot.

23. The non-transitory machine-readable storage medium of claim 22 , wherein the set of one or more characteristics include one or more of whether images are supported, whether JavaScript is supported, a type of client network application making the first request, fonts installed on the client network application making the first request, whether the client network application supports plugins, whether the client network application stores cookies, whether the client network application responds from a same IP address for various protocol requests, or any combination thereof.

24. The non-transitory machine-readable storage medium of claim 17 , wherein the operations further comprise:

receiving, at the proxy server from a second client network application, a second request for an action to be performed on the identified network resource of the origin server;

determining that the second request is not indicative of being from a second bot;

responsive to the determining that the second request is not indicative of being from a second bot, transmitting the second request to the origin server.