Problems in the analysis of user agent strings based on the browscap.ini

The list of user agents strings that can not be identified with the current Browscap.ini.

Currently, the list of unrecognized browsers and bots is getting longer and longer, as the browscap.ini file grows steadily.

It is to be considered whether browscap.ini is still the right method for the identification of a browser or bot with ever-increasing number of useragend strings. In my opinion, a method should be chosen to read the data of the User-Agend string that identifies the client by means of certain rules and a defined vocabulary. My idea, method and implementation I presented on the site User-Agent-String.

Version: 6000030
Release: Tue, 14 Aug 2018 09:20:40 +0000


Autor: , veröffentlicht: , letzte Änderung:

Kontakt

Service Infos

CMS Info Product Name:
UDOs Webserver
Version:
0.4.2.1
Description:
All in one Webserver
Copyright:
Udo Schmal
Compilation:
So, 21 Okt 2018 21:59:50
Development Info IDE:
Lazarus LCL 2.1.0.0
Compiler:
Free Pascal FPC 3.3.1
compiled for:
OS:Linux, CPU:x86_64
Hardware Info Model:
ASRock A330ION
CPU Name:
Intel(R) Atom(TM) CPU 330 @ 1.60GHz
CPU Type:
x86_64, 1 physical CPU(s), 2 Core(s), 4 logical CPU(s), 1599.996 MHz
System Info OS:
Ubuntu 18.04.1 LTS bionic