Skip to main content
CLI man page: safesquid-buitins(5)
Suggested Profiles (safesquid-buitins(5)) shows built-in profile ideas you can pick when configuring cookie-related policy. It is a UI-only naming aid — no C++ section loads this configuration at runtime.
To enforce cookie behaviour, configure Cookie filter and reference the same tag names in Access Profiles where cookie_profiles is used.

What it does and does not do

  • Does — Show labels administrators can pick when configuring Cookie filtering or Access Profiles cookie_profiles fields.
  • Does not — Enforce policy, add connection tags, or appear in the request pipeline.

Subsections

  • Default Policies — Suggested starting entries under Suggested cookie profile tags. Each row defines an example tag name (for example READ ONLY) for the Web UI picker.

Entry fields

  • Enabled — UI-only row visibility in the suggested list. Does not affect proxy behaviour.
  • Comment — Label shown in the Cookie Filtering profile-tag picker.
  • Suggested cookie profile tags — Example tag name for the dropdown. Pair with deny rows under Cookie filter and Access Profiles cookie_profiles.

Examples

  • Suggested Profiles lists READ ONLY
  • Cookie filter Deny row uses cookie profile tag READ ONLY for outbound cookies you want blocked
  • Access Profiles assigns users the matching cookie_profiles tag
Result: the suggestion is only a naming aid; effective block comes from Cookie filter + Access Profiles, not from Suggested Profiles alone.

How to verify

  1. Open Cookie filter — confirm the tag appears in the cookie profile picker after you add it under Suggested Profiles.
  2. Configure a Deny row and Access Profiles cookie_profiles with the same tag; reproduce a request with matching cookies.
  3. Detailed logs should show cookie filter outcome — Suggested Profiles alone produces no log lines.

See also

CLI: man safesquid-buitins