A URL filtering method and device

Abstract

The invention discloses a uniform resource locator (URL) filtering method. The URL filtering method comprises the steps: judging whether a status code of hypertext transfer protocol (HTTP) response information belongs to a redirection status code; if the status code belongs to the redirection status code, judging whether a URL of the HTTP response information matches a preset URL; and if the URL matches the preset URL, blocking the URL. The invention further discloses a URL filtering device.

Description

technical field [0001] The invention relates to the technical field of network communication, in particular to a method and device for filtering web addresses. Background technique [0002] In recent years, the Internet has developed rapidly, and various businesses are increasingly dependent on the Internet, resulting in the emergence of many websites, including illegal websites such as phishing, pornography, and gambling. In order to ensure the security of users surfing the Internet, it is necessary to filter the website URLs, which usually include Hypertext Transfer Protocol (Hypertext Transfer Protocol, HTTP) type URLs and Secure Hypertext Transfer Protocol (Secure Hypertext Transfer Protocol, HTTPS) type URLs, and related The HTTPS URL filtering methods provided by the technology generally include three types: [0003] Mode 1, the URL filtering device parses the HTTPS protocol, extracts the domain name of the HTTPS type URL from the Client Hello field (field in the HTTP...

AI Technical Summary

Problems solved by technology

[0004] However, the HTTPS type URL filtering method provided by the related technology has the following problems: method 1 needs to parse the HTTPS protocol data, which is more complicated and consumes the performance of the URL filtering device; in addition, the blocking URL prompt page cannot be provided, and the friendliness is poor

Method 2: There are many DNS packets, and it is difficult to maintain the correspondence table between domain names and IP addresses; one IP address may correspond to multiple domain names, and the URL filtering results are inaccurate; when users visit websites, they may directly access them without going through DNS (such as modifying Hosts file), resulting in the inability to establish a correspondence table between domain names and IP addresses, and unable to perform URL filtering

Method 3: Deployment requires certain conditions, and not all HTTPS requests can be successfully hijacked, and URL filtering may not be possible; most browsers can detect that HTTPS data has been hijacked, and trigger an alarm, making users sensitive; hijacking and analysis HTTPS data is complex, which consumes the performance of URL filtering equipment

Images