Skip to main content
CLI man page: safesquid-reqProfiles(5)
The Request Types section (safesquid-reqProfiles(5)) labels HTTP requests with tags consumed by Access Profiles and other filters. It does not block traffic.

​
Core mechanics

​
Processing order

  1. Application Signatures (unless subscription expired).
  2. Domains and Urls — substring match; every matching row applies.
  3. Request Types rows — all gates must pass; every match applies.
Request Types gate flow

Request Types — row gate order

​
Domains and Urls

Tab-prefixed host+path substring find — not regex. Empty domain list or empty add/remove → row skipped. Match: Host, Referer, or Both.

​
Smart TLD

When Host Name regex misses and Smart TLD is on, same regex retried against site name (host without public suffix).
urlcommand field: parsed in configuration but never evaluated at runtime. Use Protocol or File instead.
Post Data Size: runtime logic inverts UI labels (uses Content-Length only). Treat as experimental.

​
Examples

​
Uncachable query URLs

Config: File (cgi-bin|\?), add uncachable_req.Result: URLs with query string tagged; cache policies can skip storage.

​
CONNECT method

Config: Method CONNECT, add uncachable_req.Result: tunnel requests tagged.

​
Skip categorization

Config: Domains needle partner.example, Bypass DNSBL and Categorization on.Result: matching host bypasses DNSBL and category lookup.

​
How to verify

  1. Trace Entry on one row; native logs show Added/Removed tags.
  2. Detailed logs request_profiles column.

Related topics

Request ProfilesAllow Specific YouTube Channel and its PlaylistBlock Specific YouTube ChannelArchitecture and request pipelineBypass Authentication