Problems with Android for Web Access: USER_AGENT_DALVIK

The new security bots in the hosting servers detect the web access as a virus because the html identification AI2-Post message has the chain Dalvik from the Android versions minor than 4.4 KitKat. It happens only in Android (iOS has not this problem)

If anybody has a 403_Forbidden Access mistake from their server-hosting keep attention with this issue.

:question:

hosting servers?

The solution is that the Server Support cancel this MOD_SECURITY parameter in the respective domain affected.

The internet web server where we have the programs to process the message received from our App.

Not having any issues with my servers ...

May be they have not upgraded at this moment the last update for the MOD_SECURITY? When the service support put the last update is possible you will receive this mistake 403 in your apps.

The app mistake has only the text "403 - Forbidden access". To find what that is for the DELVIK bot is very difficault to detect it.

You should be able to set a User-Agent header for the Web request to something that makes sense for your application to override the OS provided default.

I tried but it was not possible to avoid the MOD_SECURITY bot control in the server firewall.

How?

It would really help if you provided a screenshot of your relevant blocks, so we can see what you are trying to do, and where the problem may be.

To get an image of your blocks, right click in the Blocks Editor and select "Download Blocks as Image". You might want to use an image editor to crop etc. if required. Then post it here in the community.

Taifun


Trying to push the limits! Snippets, Tutorials and Extensions from Pura Vida Apps by icon24 Taifun.

From always I have only this Header Block:

After I have tested whit this:


But the problem was the same whith the 403-Forbiden access.

The issue was solved only when my support Internet Server canceled the inspect bot DELVIK in my domain. May be there is other Header to test but I don't know.

The suggestion was

I do not see you setting it... why?

Yes, it is

User-Agent

Taifun

I haven't been able to disable the 403-Forbiden access block caused by the DEVILK bot with the POST message in the Ai2 Block Header. This issue can only be managed on my web server's Apache server by modifying the MODSECURITY.conf file, and I don't have permissions to do so; only the admin of my server has them.

What about providing a screenshot of your relevant blocks including the User-Agent header?

Try one of these

Taifun