#useragent

イラスト付きで簡単に使用できるUserAgent切り替えアドオン「User-Agent Switcher」のご紹介です。

(more…)

Fix: illegitimate traffic from user agent Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.0.10) Gecko/2009042316 Firefox/3.0.10 (.NET CLR 3.5.30729) #solution #fix #programming

illegitimate traffic from user agent Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.0.10) Gecko/2009042316 Firefox/3.0.10 (.NET CLR 3.5.30729)

This is a rapidly changing event that has no answer yet.

Please do not post your findings or assumptions as answers; reserve the answer field for when you actually have an answer.

If you have something newto add, please edit it directly in to the…

The User-Agent that Authorize.Net send during a "Silent Post" is empty.

Most application firewalls (used for PCI compliance) are configured to block blank/empty user-agents.

Open Web Application Security Project (OWASP) blocks empty user agents by default: https://github.com/SpiderLabs/owasp-modsecurity-crs/blob/master/base_rules/modsecurity_crs_21_protocol_anomalies.conf http://stackoverflow.com/a/10139985/693068

#Missing/Empty User-Agent Header #-=[ Rule Logic ]=- #These rules will first check to see if a User-Agent header is present. #The second check is to see if a User-Agent header exists but is empty.

So does WP WAF (WordPress Application Firewall): https://github.com/guelfoweb/wp-waf and 5G Blacklist http://perishablepress.com/5g-blacklist-2013/ and Bad Behavior http://bad-behavior.ioerror.us/

I report this issue 15+ months ago via Twitter & merchant feedback form.  (NOTE: Feedback form only accepts 1,000 characters.) https://twitter.com/AuthorizeNet/status/309788328541167618

We wasted time troubleshooting why silent posts weren't being posted. Are there any valid/legitimate reasons why a blank user agent isn't passed? If no change is to be made, could you please update documentation throughout the Authorize.Net website and state that "websites running application firewalls may be impacted and may have to disable some rules in order to accept silent posts."

iPhoneでsafariのバージョンを判別する際に、 ユーザーエージェントでVersionの値を使っていると、chromeブラウザで表示した場合JSエラーが起きる。

■iOS7.0のSafariが返すuserAgent

Mozilla/5.0 (iPhone; CPU iPhone OS 7_0 like Mac OS X) AppleWebKit/537.51.1 (KHTML, like Gecko) Version/7.0 Mobile/11A465 Safari/9537.53

■Chrome for iOSが返すuserAgent

Mozilla/5.0 (iPhone; CPU iPhone OS 7_0 like Mac OS X) AppleWebKit/537.51.1 (KHTML, like Gecko) CriOS/30.0.1599.12 Mobile/11A465 Safari/8536.25

太字部分で示す通り、Chrome for iOSではVersionの記述が無いのでエラーとなっていた。判別するなら、Versionの有無を確認してからか、 iPhone OSの値を使って判別するのが良い。

参考

【Chrome for iOSのユーザーエージェントについて】

NTLM を有効にして、サイトにログインできるようになっても、User Agent の判別で追い返されたのでは、Firefox でも見えるかもしれないサイトのチェックができないですよね？

そんな時には User Agent Switcher を使って、サイトに対して IE を偽装してみます。

うまくいけば表示できるかもしれません。