Blog Post

The Qrew Blog
2 MIN READ

What is the [User Agent] Field in Quickbase Audit Logs?

JoshMiller1's avatar
JoshMiller1
Quickbase Staff
3 days ago

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:

PartMeaning
Mozilla/5.0This 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.36Rendering 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.0Browser engine version: Chromium version 134.0.0.0.
Safari/537.36Compatibility tag indicating Safari WebKit behavior (same as AppleWebKit version).
Edg/134.0.0.0Microsoft 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

Edg/ =  Microsoft Edge

Chrome/ without Edg =

  Google Chrome

Firefox/ =

  Mozilla Firefox

Safari/ (without Chrome or Edg) =

  Apple Safari

Splitting the User Agent into Useful Fields:

Field NameWhat It CapturesExample Value
Browser NameThe name of the browserMicrosoft Edge
Browser VersionFull version of the browser134.0.0.0
Operating SystemThe OS platformWindows 10
ArchitectureCPU architecture type64-bit (x64)
Device TypeDesktop, Mobile, or TabletDesktop
Engine NameRendering engine
(WebKit, Blink, Gecko, etc.)
WebKit (Chromium-based)
Engine VersionRendering engine version537.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
Browser Name:Microsoft Edge
Browser Version:134.0.0.0
Operating System:Windows 11
Architecture:64-bit (x64)
Device Type:Desktop
Engine:WebKit (Chromium)
Engine Version:537.36

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.0
No CommentsBe the first to comment