head	1.4;
access;
symbols
	RELEASE_8_3_0:1.2
	RELEASE_9_0_0:1.2;
locks; strict;
comment	@# @;


1.4
date	2012.05.15.02.04.47;	author sunpoet;	state Exp;
branches;
next	1.3;

1.3
date	2012.04.09.17.43.00;	author sunpoet;	state Exp;
branches;
next	1.2;

1.2
date	2011.11.15.15.50.46;	author sunpoet;	state Exp;
branches;
next	1.1;

1.1
date	2011.11.12.16.45.51;	author sunpoet;	state Exp;
branches;
next	;


desc
@@


1.4
log
@- Update to 0.35

Changes:	http://search.cpan.org/dist/Parse-HTTP-UserAgent/Changes
@
text
@SHA256 (Parse-HTTP-UserAgent-0.35.tar.gz) = 39a6842f5807eb8ffa4cbc9afe9e53eceaadbcfbf7f09d7b100bd51f9f67a4bf
SIZE (Parse-HTTP-UserAgent-0.35.tar.gz) = 79353
@


1.3
log
@- Update to 0.34
- Add TEST_DEPENDS

Changes:	http://search.cpan.org/dist/Parse-HTTP-UserAgent/Changes
Feature safe:	yes
@
text
@d1 2
a2 2
SHA256 (Parse-HTTP-UserAgent-0.34.tar.gz) = 8303451b7a61f863bad2052667e0d1d065e5d64a5504e96835cd558167732820
SIZE (Parse-HTTP-UserAgent-0.34.tar.gz) = 73025
@


1.2
log
@- Update to 0.33

Changes:	http://search.cpan.org/dist/Parse-HTTP-UserAgent/Changes
Feature safe:	yes
@
text
@d1 2
a2 2
SHA256 (Parse-HTTP-UserAgent-0.33.tar.gz) = f8f98e20e65fa364b8e6b6451ab0c5ff2f44ecbab3e2a259e7f4db3079734137
SIZE (Parse-HTTP-UserAgent-0.33.tar.gz) = 71435
@


1.1
log
@- Add p5-Parse-HTTP-UserAgent 0.32

Parse::HTTP::UserAgent implements a rules-based parser and tries to identify
MSIE, FireFox, Opera, Safari & Chrome first. It then tries to identify Mozilla,
Netscape, Robots and the rest will be tried with a generic parser. There is also
a structure dumper, useful for debugging.

User agent strings are a complete mess since there is no standard format for
them. They can be in various formats and can include more or less information
depending on the vendor's (or the user's) choice. Also, it is not dependable
since it is some arbitrary identification string. Any user agent can fake
another. So, why deal with such a useless mess? You may want to see the choice
of your visitors and can get some reliable data (even if some are fake) and
generate some nice charts out of them or just want to send an HttpOnly cookie if
the user agent seems to support it (and send a normal one if this is not the
case). However, browser sniffing for client-side coding is considered a bad
habit.

WWW: http://search.cpan.org/dist/Parse-HTTP-UserAgent/

Feature safe:	yes
@
text
@d1 2
a2 2
SHA256 (Parse-HTTP-UserAgent-0.32.tar.gz) = ed9261ac790037e2cb4fbcfb5dde9fa8c115ef59cf4709e08346d4dc56439a2f
SIZE (Parse-HTTP-UserAgent-0.32.tar.gz) = 71384
@

