The Qrew Blog
2 MIN READ
What is the [User Agent] Field in Quickbase Audit Logs?
JoshMiller1
3 days agoQuickbase Staff
When reviewing audit logs in Quickbase, the User Agent field may seem complex at first glance. However, with the right breakdown, it reveals powerful information about who or what accessed your applications. Let’s walk through an example together.
Example User Agent:
Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/134.0.0.0 Safari/537.36 Edg/134.0.0.0
Full Breakdown:
Part | Meaning |
---|---|
Mozilla/5.0 | This is a legacy prefix. Originally meant "compatible with Mozilla browsers." Today it just signals "I'm a web browser" for compatibility. |
(Windows NT 10.0; Win64; x64) | Operating system and architecture: Windows 10, 64-bit (x64 architecture). |
AppleWebKit/537.36 | Rendering engine: WebKit (like Safari and Chrome use), version 537.36. Means the browser uses WebKit-based layout. |
(KHTML, like Gecko) | Says the engine behaves like Gecko (used by Firefox). Another compatibility statement. |
Chrome/134.0.0.0 | Browser engine version: Chromium version 134.0.0.0. |
Safari/537.36 | Compatibility tag indicating Safari WebKit behavior (same as AppleWebKit version). |
Edg/134.0.0.0 | Microsoft Edge browser, Chromium-based, version 134.0.0.0. |
What This Tells Us:
- Operating System: Windows 10
- Architecture: 64-bit machine (x64)
- Browser: Microsoft Edge (Chromium-based)
- Browser Version: 134.0.0.0
- Rendering Engine: WebKit (via Chromium 134)
- Note: Although Chrome and Safari are mentioned, the real browser is revealed by the Edg/ identifier.
Quick Tip: Identifying Browsers
|
Splitting the User Agent into Useful Fields:
Field Name | What It Captures | Example Value |
---|---|---|
Browser Name | The name of the browser | Microsoft Edge |
Browser Version | Full version of the browser | 134.0.0.0 |
Operating System | The OS platform | Windows 10 |
Architecture | CPU architecture type | 64-bit (x64) |
Device Type | Desktop, Mobile, or Tablet | Desktop |
Engine Name | Rendering engine (WebKit, Blink, Gecko, etc.) | WebKit (Chromium-based) |
Engine Version | Rendering engine version | 537.36 |
How This Would Look When Split:
Raw User Agent:
Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/134.0.0.0 Safari/537.36 Edg/134.0.0.0
|
Conclusion:
The User Agent field in Quickbase audit logs isn't just technical noise — it's a treasure trove of insights. By understanding how to read it, you can better identify user environments, troubleshoot access issues, and improve your governance practices within Quickbase.
Next time you see a long User Agent string, take a closer look — the story it tells might surprise you!
Updated 3 days ago
Version 1.0JoshMiller1
Quickbase Staff
Joined September 15, 2022
The Qrew Blog
Where The Qrew can learn of upcoming events and product updates.