Patent classifications
H04L67/563
Methods and apparatus to prevent illicit proxy communications from affecting a monitoring result
Methods, apparatus, systems and articles of manufacture to prevent illicit proxy communications from affecting a monitoring result are disclosed. An example method includes accessing a log of communications of a proxy server, the log of communications including a plurality of records, each of the plurality of records corresponding to a requesting device that transmitted a communication to the proxy server, identifying a first internet protocol (IP) address subnet in the log of communications, the first IP address subnet associated with a block of IP addresses, filtering the plurality of records for a first set of records associated with communications originating from the first IP address subnet, and in response to determining the first set of records does not include a record associated with a heartbeat communication, adding the first IP address subnet to a blacklist of the proxy server.
Methods and apparatus to prevent illicit proxy communications from affecting a monitoring result
Methods, apparatus, systems and articles of manufacture to prevent illicit proxy communications from affecting a monitoring result are disclosed. An example method includes accessing a log of communications of a proxy server, the log of communications including a plurality of records, each of the plurality of records corresponding to a requesting device that transmitted a communication to the proxy server, identifying a first internet protocol (IP) address subnet in the log of communications, the first IP address subnet associated with a block of IP addresses, filtering the plurality of records for a first set of records associated with communications originating from the first IP address subnet, and in response to determining the first set of records does not include a record associated with a heartbeat communication, adding the first IP address subnet to a blacklist of the proxy server.
Resilient distributed storage system
A distributed data storage system that includes endpoint nodes, gateway nodes, and one or more gateway name servers. A gateway name server receives from clients resolution requests to resolve to a gateway node and resolves the resolution requests to a gateway node address of a gateway node. A gateway node receives client requests to access an endpoint node and redirects the requests to endpoint nodes identified by a gateway node whose address was resolved to by a gateway name server. An endpoint node receives from a client a retrieval request to retrieve data based on being redirected to the endpoint node. When a retrieval request is received and the endpoint node stores the data, the endpoint node sends the data to the client. When a retrieval request is received and the endpoint node does not store the data, the endpoint node forwards the retrieval request to another endpoint node.
Inline SPF service provider designation
Sender Policy Framework (SPF) is one of the most widely used methods of distinguishing electronic mail that is authorized by the purported sending domain from unauthorized mail. SPF policies are published into a domain's DNS and then looked up and evaluated by mail receivers. Due to the complexity and limitations of the SPF specification, implementation mistakes are widespread. This problem is compounded by the common practice of nesting SPF policies which introduces hidden risks, particularly exceeding DNS lookup limits. To address these issues, inline service provider designation may be configured to capture the benefits of existing techniques without their associated costs. Additionally, the domain owner may enjoy simplified SPF service provider onboarding and policy failover redundancy to protect against SPF service provider disruptions, thus improving policy availability uptime.
Inline SPF service provider designation
Sender Policy Framework (SPF) is one of the most widely used methods of distinguishing electronic mail that is authorized by the purported sending domain from unauthorized mail. SPF policies are published into a domain's DNS and then looked up and evaluated by mail receivers. Due to the complexity and limitations of the SPF specification, implementation mistakes are widespread. This problem is compounded by the common practice of nesting SPF policies which introduces hidden risks, particularly exceeding DNS lookup limits. To address these issues, inline service provider designation may be configured to capture the benefits of existing techniques without their associated costs. Additionally, the domain owner may enjoy simplified SPF service provider onboarding and policy failover redundancy to protect against SPF service provider disruptions, thus improving policy availability uptime.
Reducing redirects
Methods, systems, and apparatus, including computer programs encoded on a computer storage medium, for reducing redirects. In one aspect, a method includes receiving request data indicating that a user device has requested a content item. The request data specifies other data processing apparatus to which user interactions with the content item are to be reported. The content item includes a reference to a resource that is requested in response to user interaction with the content item. Response data is provided. The response data includes data that cause presentation of the content item. Interaction data is received specifying user interaction with the content item occurred. Redirect data is provided that cause the user device to be redirected to the resource. Reporting data is provided to the other data processing apparatus, specifying user interaction with the content item occurred. The reporting data is provided asynchronously relative to the redirect data.
Reducing redirects
Methods, systems, and apparatus, including computer programs encoded on a computer storage medium, for reducing redirects. In one aspect, a method includes receiving request data indicating that a user device has requested a content item. The request data specifies other data processing apparatus to which user interactions with the content item are to be reported. The content item includes a reference to a resource that is requested in response to user interaction with the content item. Response data is provided. The response data includes data that cause presentation of the content item. Interaction data is received specifying user interaction with the content item occurred. Redirect data is provided that cause the user device to be redirected to the resource. Reporting data is provided to the other data processing apparatus, specifying user interaction with the content item occurred. The reporting data is provided asynchronously relative to the redirect data.
System and method for improving content fetching by selecting tunnel devices
A method for fetching a content from a web server to a client device is disclosed, using tunnel devices serving as intermediate devices. The tunnel device is selected based on an attribute, such as IP Geolocation. A tunnel bank server stores a list of available tunnels that may be used, associated with values of various attribute types. The tunnel devices initiate communication with the tunnel bank server, and stays connected to it, for allowing a communication session initiated by the tunnel bank server. Upon receiving a request from a client to a content and for specific attribute types and values, a tunnel is selected by the tunnel bank server, and is used as a tunnel for retrieving the required content from the web server, using standard protocol such as SOCKS, WebSocket or HTTP Proxy. The client only communicates with a super proxy server that manages the content fetching scheme.
System and method for improving content fetching by selecting tunnel devices
A method for fetching a content from a web server to a client device is disclosed, using tunnel devices serving as intermediate devices. The tunnel device is selected based on an attribute, such as IP Geolocation. A tunnel bank server stores a list of available tunnels that may be used, associated with values of various attribute types. The tunnel devices initiate communication with the tunnel bank server, and stays connected to it, for allowing a communication session initiated by the tunnel bank server. Upon receiving a request from a client to a content and for specific attribute types and values, a tunnel is selected by the tunnel bank server, and is used as a tunnel for retrieving the required content from the web server, using standard protocol such as SOCKS, WebSocket or HTTP Proxy. The client only communicates with a super proxy server that manages the content fetching scheme.
DIGITAL COMMUNICATION MODULE FOR A SELF-CONTAINED MEDICAL DEVICE COMMUNICATION PLATFORM
A digital communication module for a self-contained medical device communication platform is disclosed herein. In an example, a digital communication module is communicatively coupled to a therapy module of a medical device for relaying medical device data to an electronic medical record (“EMR”) server that is connected to a medical network. The digital communication module is connected to at least one other digital communication module via a wireless proprietary network that is separate from the medical network. The digital communication module determines that the medical device data from the medical device is to be transmitted, via the wireless proprietary network, to one of the other digital communication modules that is connected to the EMR server via the medical network. The other of the digital communication modules receives, and then routes the medical device data to the EMR server via the medical network.