Granted Patent B2

US 12,332,960 · App. 17/572,090 · Granted Jun 17, 2025

Inventors: Derry Shribman (Tel Aviv, IL); Ofer Vilenski (Moshav Hadar Am, IL)

Assignee: BRIGHT DATA LTD.

G06F16/955G06F9/547G06F16/909G06F16/9558G06F16/9566H04L1/00H04L67/01H04L67/02H04L67/1021H04L67/146H04L67/568H04L69/40H04L61/59H04L67/56

Abstract

Claims (29)

1. A method for data extraction and gathering from a web server, comprising:

receiving, by a first device from a user device, a request;

requesting, by the first device from a second device, an IP address from a database that stores a list of IP addresses;

accessing, by the second device, the database;

choosing, by the second device, an IP address from the list;

providing, by the second device to the first device, the chosen IP address;

sending, by the first device, the request to a proxy device that is addressed by the chosen IP address;

obtaining, by the proxy device, a reply from the web server;

forwarding, by the proxy device to first device, the reply;

analyzing, by the first device, the reply; and

determining, by the first device, pursuant to the analysis, if the reply is proper,

wherein, if the reply is proper, the reply is sent to the user device,

wherein, if the reply is not proper, the method repeats the data extraction and gathering from the web server,

wherein the repeating comprises deciding, pursuant to the analysis of the reply, if an adjustment of the request is needed,

wherein the reply is a Hypertext Transfer Protocol (HTTP) reply that comprises a response body, and the analyzing comprises analyzing of a HTTP reply status code in the HTTP header of the reply or a response body in the reply, and

wherein if the reply is not proper, the repeated data extraction and gathering from the web server is using different parameters that are deemed relevant for obtaining a proper reply.

2. The method of claim 1 , wherein the reply is determined as a proper response responsive to a status code of 2xx or 3xx, or wherein the reply is determined as a not proper response responsive to a status code of 5xx.

3. The method of claim 1 , wherein the reply is determined as a not proper response responsive to a status code of HTTP 404 error message.

4. The method of claim 3 , wherein if the reply is proper, the reply is passed to a next data processing step.

5. The method of claim 3 , wherein if the reply is not proper, the repeated data extraction and gathering from the web server is using a different scheme.

6. The method of claim 1 , wherein if the reply is not proper, the repeated data extraction and gathering from the web server is using the same parameters or the same scheme.

7. The method of claim 1 , wherein the forwarding of the reply, by the proxy device to first device, comprising forwarding without modifying or analyzing of the reply.

8. The method of claim 1 , wherein a communication with the user device, with the first device, with the second device, or with the proxy device, is using a HTTP protocol.

9. The method of claim 1 , further comprising using, and communicating with, more than one proxy server.

10. The method of claim 1 , further comprising reusing the proxy device for multiple requests.

11. The method of claim 1 , wherein the analyzing of the reply comprises forming analyzing reply parameters and identifying best practices to be used in the repeated data extraction and gathering.

12. The method of claim 11 , wherein different parameters are used in the repeated data extraction and gathering.

13. The method of claim 1 , further comprising geolocating of the proxy device.

14. The method of claim 1 , wherein the reply is determined as not proper if it contains a proper content or it does not contain any error.

Assignments (2)

Continuity (6)

References Cited (400)