SYSTEMS AND METHODS FOR MANAGING NETWORK RESOURCE REQUESTS
Systems and methods are configured to control network and content access. A URL rewrite engine receives a content request from a client device coupled to a local network. A first set of rules, the first set of rules comprising a combination of meta rules and content rules, is accessed. The URL rewrite engine applies the first set of rules to the request and/or the requested content to determine how the content request and/or the content are to be processed. Based at least in part on the application of the first set of rules, rewriting the request, denying the request, or modifying the requested content is performed.
1 . A computer-implemented method of controlling network access, the method comprising:
receiving at a URL rewrite engine comprising hardware a content request from a client device coupled to a local network;
accessing, by the URL rewrite engine, business rules, the business rules comprising a combination of meta rules and content rules;
applying, by the URL rewrite engine, the business rules to the request or the requested content, or both the request and the requested content, to determine how the content request, the content, or both the content request and the content, are to be processed; and
based at least in part on the application of the business rules, rewriting the request, denying the request, or modifying the requested content, by the URL rewrite engine.
2 . The method as defined in claim 1 , wherein the meta rules comprise a non-processing rule with respect to at least one URL.
3 . The method as defined in claim 1 , wherein the meta rules comprise a URL modification rule with respect to at least one URL.
4 . The method as defined in claim 1 , wherein the meta rules comprise a skip-proces sing rule with respect to at least one request.
5 . The method as defined in claim 1 , wherein the meta rules comprise a rule specifying that requests from a first IP address are authorized to access the local network.
6 . The method as defined in claim 1 , wherein the meta rules comprise a rule specifying what schema is to be used for at least a first communication with the client device.
7 . The method as defined in claim 1 , wherein the meta rules comprise a rule specifying a condition for cookie modification.
8 . The method as defined in claim 1 , wherein the meta rules comprise a rule specifying a condition for header modification, addition, or deletion.
9 . The method as defined in claim 1 , wherein the meta rules comprise a rule specifying a condition for code modification, addition, or deletion in content being provided to the client device.
10 . The method as defined in claim 1 , wherein the meta rules comprise a rule specifying a condition for turning on or off a content cache.
11 . The method as defined in claim 1 , wherein the content rules comprise a rule specifying a first type of content processing based at least in part on code included in the content.
12 . The method as defined in claim 1 , wherein the content rules comprise a rule specifying a first type of processing based at least in part on a URL included in the request.
13 . The method as defined in claim 1 , wherein the content rules comprise a rule specifying a first type of content processing based at least in part on a location of the client device.
14 . The method as defined in claim 1 , wherein the client device does not need to be specifically configured to access the URL rewrite engine.
15 . The method as defined in claim 1 , wherein the client device may access at least one resource associated with a corresponding requested URL without the URL being forward to the resource by the URL rewrite engine.
16 . The method as defined in claim 1 , wherein the URL rewrite engine hosts webpages corresponding to a domain or subdomain of an external resource which can be accessed by the client device using a URL for the external resource.
17 . The method as defined in claim 1 , wherein the URL rewrite engine is configured to rewrite at least one requested URL so that the URL cannot be resolved by an external domain name server (DNS).
18 . A system comprising:
a data store configured to at least store computer-executable instructions; and
a hardware processor in communication with the data store, the hardware processor configured to execute the computer-executable instructions to at least:
receiving a content request from a client device coupled to a local network;
accessing a first set of rules, the first set of rules comprising a combination of meta rules and content rules;
applying the first set of rules to the request or the requested content, or both the request and the requested content, to determine how the content request, the content, or both the content request and the content, are to be processed; and
based at least in part on the application of the first set of rules, modifying the request, denying the request, or modifying the requested content.
19 . The system as defined in claim 17 , wherein the meta rules comprise a non-processing rule with respect to at least one URL.
20 . The system as defined in claim 17 , wherein the meta rules comprise a URL modification rule with respect to at least one URL.
21 . The system as defined in claim 17 , wherein the meta rules comprise a skip-processing rule with respect to at least one request.
22 . The system as defined in claim 17 , wherein the meta rules comprise a rule specifying that requests from a first IP address are authorized to access the local network.
23 . The system as defined in claim 17 , wherein the meta rules comprise a rule specifying what schema is to be used for at least a first communication with the client device.
24 . The system as defined in claim 17 , wherein the meta rules comprise a rule specifying a condition for cookie modification.
25 . The system as defined in claim 17 , wherein the meta rules comprise a rule specifying a condition for header modification, addition, or deletion.
26 . The system as defined in claim 17 , wherein the meta rules comprise a rule specifying a condition for code modification, addition, or deletion in content being provided to the client device.
27 . The system as defined in claim 17 , wherein the meta rules comprise a rule specifying a condition for turning on or off a content cache.
28 . The system as defined in claim 17 , wherein the content rules comprise a rule specifying a first type of content processing based at least in part on code included in the content.
29 . The system as defined in claim 17 , wherein the content rules comprise a rule specifying a first type of processing based at least in part on a URL included in the request.
30 . The system as defined in claim 17 , wherein the content rules comprise a rule specifying a first type of content processing based at least in part on a location of the client device.
31 . The system as defined in claim 17 , wherein the client device does not need to be specifically configured to access the URL rewrite engine.
32 . The system as defined in claim 17 , wherein the client device may access at least one resource associated with a corresponding requested URL without the URL being forward to the resource by the URL rewrite engine.
33 . The system as defined in claim 17 , wherein the URL rewrite engine hosts webpages corresponding to a domain or subdomain of an external resource which can be accessed by the client device using a URL for the external resource.
34 . A non-transitory computer-readable storage medium storing computer-executable instructions that when executed by a computing device cause the computing device to perform operations comprising:
receiving a content request from a client device coupled to a local network;
accessing a first set of rules, the first set of rules comprising a combination of meta rules and content rules;
applying the first set of rules to the request or the requested content, or both the request and the requested content, to determine how the content request, the content, or both the content request and the content, are to be processed; and
based at least in part on the application of the first set of rules, modifying the request, denying the request, or modifying the requested content.