AppNeta HTTP Monitoring - User Agent String

Products

• AppNeta

Issue/Introduction

It may be required to manually set the User Agent String of HTTP Monitoring due to various reasons such as curl being actively prevented from connecting to the web application or simply a necessity to manually manipulate it.

Resolution

As with curl or any browser it's possible to override how the request appears as in override what type of client it is when the request to access the page.    

In this case I told curl to use a Chrome v102 request header:

The exact entries in the above image are as follows:

user-agent
Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/102.0.5005.61 Safari/537.36

 

With the above User Agent String in place, the HTTP Monitoring tests will be presented as if it were the Chrome Browser instead of curl.