User-Agent Detect

The ua-detect analysis controller parses the HTTP User-Agent header to identify browser, OS, device type, and bots.

Configuration

analysisControllers:
  - name: user-agent
    type: ua-detect
    # settings:
    #   enableFallback: true  # use regex-based ua-parser when the primary parser marks UA as unknown
    #   cacheEnabled: true    # disable to skip UA result caching (enabled by default)

Upstream Headers Injected

Browser information

• X-UA-Browser — Browser name (e.g., Chrome)
• X-UA-Browser-Version — Full version string
• X-UA-Browser-Major — Major version
• X-UA-Browser-Minor — Minor version
• X-UA-Browser-Patch — Patch version

Operating system

• X-UA-OS-Name — OS name (e.g., Windows, macOS, Linux)
• X-UA-OS-Version — Full OS version
• X-UA-OS-Major — Major version
• X-UA-OS-Minor — Minor version
• X-UA-OS-Platform — Platform architecture

Device information

• X-UA-Device-Type — One of: desktop, mobile, tablet, bot, tv, unknown
• X-UA-Device-Mobile — Boolean (true/false)
• X-UA-Device-Tablet — Boolean
• X-UA-Device-Desktop — Boolean
• X-UA-Device-TV — Boolean
• X-UA-Device-Model — Device model (when available)

Bot detection

• X-UA-Bot-Name — Bot name (when detected)
• X-UA-Bot-URL — Bot URL/homepage

Parser Pipeline

• Primary parser: mileusna/useragent (fast path).
• Optional fallback: ua-parser/uap-go used when enableFallback is true and the primary parser reports an unknown UA.
• Parsed results are cached by UA string when cacheEnabled is true (default).

Use Cases

• Block or rate-limit bots
• Device-specific access policies
• Browser compatibility checks
• Analytics and user insights
• Mobile vs desktop routing

Requirements

• None (no external dependencies)