QUOTE(jenga201 @ Nov 10 2013, 08:29)

CODE
2013-11-10T00:52:33Z [WARN] {5998469/xxxx} Invalid request type 'apple-touch-icon-precomposed.png'.
2013-11-10T00:52:34Z [WARN] {5998482/xxxx} Invalid request type 'apple-touch-icon.png'.
This is normal and harmless: the iOS browser try to access proprietary features that are not supported by the official H@H implementation. It does that automatically, without user intervention.
QUOTE(jenga201 @ Nov 10 2013, 08:29)

CODE
2013-11-10T05:48:04Z [WARN] Invalid kvPair: keystamp%3d1384062600-6e828aa931
2013-11-10T05:48:34Z [WARN] Invalid kvPair: keystamp%3d1383460800-05bf677cf4
Again, normal and harmless: the official H@H implementation is not fully compliant with the HTTP/1.1 specifications, so it sometimes fails to extract the parameters from some (exotic) HTTP requests. This is a known limitation.
This post has been edited by Hairs Fan: Nov 11 2013, 04:08