User agent parsing


Author
Message
Dave
Dave
Supreme Being (1M reputation)Supreme Being (1M reputation)Supreme Being (1M reputation)Supreme Being (1M reputation)Supreme Being (1M reputation)Supreme Being (1M reputation)Supreme Being (1M reputation)Supreme Being (1M reputation)Supreme Being (1M reputation)
Group: Administrators
Posts: 13K, Visits: 104K
The platform / browser sniffing is done in JavaScript. You can glean the code directly by looking at a launch page's source. For Inquisit 4 Web, see e.g. view-source:https://www.millisecond.com/download/library/v4/IAT/IAT.web

The functions of interest are in the

/*****************************************************
UTILILTY FUNCTIONS
******************************************************/

section towards the bottom (starting around line 950).

Hope this helps.

Edited 8 Years Ago by Dave
lakeside
lakeside
Guru (7.2K reputation)Guru (7.2K reputation)Guru (7.2K reputation)Guru (7.2K reputation)Guru (7.2K reputation)Guru (7.2K reputation)Guru (7.2K reputation)Guru (7.2K reputation)Guru (7.2K reputation)
Group: Forum Members
Posts: 34, Visits: 121
Are you able to share the parsing/logic applied to the user agent string by Millisecond to determine if a subject's hardware/software meet the Inquisit requirements? We're building a front-end page to our Inquisit web tasks and would like to stop non-compliant users from hitting Millisecond's website.



GO

Merge Selected

Merge into selected topic...



Merge into merge target...



Merge into a specific topic ID...




Reading This Topic

Explore
Messages
Mentions
Search