http://browsers.garykeith.com/index.asp

The Browsecap project is behind the browser detection.

However, I'd avoid use of the internal PHP function. Using the internal 
function means that it is up to the system administrator to keep the 
browscap.ini file. And on shared hosting, you're dependent on the 
hosting provider, most of whom barely ever update that file.

There is an alternate way to use the file, you can search the internet 
for it. It's actually just a real simple php function to replace the 
internal one.
Though I notice that there is a project on google code that seams to 
extend with a few more features: http://code.google.com/p/phpbrowscap/

~Daniel Friesen (Dantman, Nadir-Seen-Fire)
~Profile/Portfolio: http://nadir-seen-fire.com
-The Nadir-Point Group (http://nadir-point.com)
--It's Wiki-Tools subgroup (http://wiki-tools.com)
--The ElectronicMe project (http://electronic-me.org)
-Wikia ACG on Wikia.com (http://wikia.com/wiki/Wikia_ACG)
--Animepedia (http://anime.wikia.com)
--Narutopedia (http://naruto.wikia.com)

Aryeh Gregor wrote:
> On Sun, Nov 23, 2008 at 8:13 PM, Gregory Maxwell <[EMAIL PROTECTED]> wrote:
>   
>> Can you suggest a good user-agent scrubber? Many user-agents strings
>> have various degrees of private/semi-private data stuffed into them.
>>
>> I've looked at publishing user-agent stats for Wikimedia site before,
>> but realized that I don't have enough knowledge to safely canonicize
>> them without throwing out a ton of information. (I.e. I could break
>> down IE vs Firefox vs Opera vs Safari; but if you want to know about
>> less common user agents I'm not quite sure what information can be
>> safely released)
>>     
>
> PHP has a built-in function that does this:
>
> http://www.php.net/manual/en/function.get-browser.php
>
> It's apparently configurable using a .ini file.  Probably there are
> some fairly good ones available.
>   


_______________________________________________
Wikitech-l mailing list
[email protected]
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Reply via email to