android - Can I safely block Dalvik browser agent requests? -


i've noticed when users on android-os devices visit site, there's 2 requests happening on each page. first normal browser, , second "dalvik". example:

"get / http/1.1" 200 2126 "-" "mozilla/5.0 (linux; android 5.0.2; samsung sm-g925f/g925fxxu1aod8 build/lrx22g) applewebkit/537.36 (khtml, gecko) samsungbrowser/3.0 chrome/38.0.2125.102 mobile safari/537.36" 1229 2802

"get / http/1.1" 200 2117 "-" "dalvik/2.1.0 (linux; u; android 5.0.2; sm-g925f build/lrx22g)" 546 8729

from understanding of this, first request actual browser, , other virtual machine (dalvik) running browser. problem dalvik request doesn't use same cookies, and/or post data, , triggers errors server side. example when user registers account. normal browser sends through post data, dalvik request on action url. similarly, if user logged in, dalvik try on permission based page, may redirect somewhere else because there's no session it.

the user doesn't experience real problems (from can tell), however, notice attempts in our error logging. question is: can safely block access attempts if browser agent indicates "dalvik/..*"? there adverse affects user? considering dalvik-related requests aren't reposting real data or carrying session, seems unlikely. hoping more experience android can provide feedback on it, example, should issue specific http header/status code, "401 unauthorized" or "400 bad request"?

any appreciated.

this linux shell samsung phones. os listed "linux 3.4.0-7500527 (dalvik 2.1.0)" , it's samsung galaxy s5. set duplicate of site (even minimal) gets receiving 501, perhaps? that, should easy find out.


Comments

Popular posts from this blog

sequelize.js - Sequelize group by with association includes id -

android - Robolectric "INTERNET permission is required" -

java - Android raising EPERM (Operation not permitted) when attempting to send UDP packet after network connection -