Forum Discussion
User-Agent: Non-browser Client
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.1; WOW64; Trident/5.0; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; Media Center PC 6.0; .NET4.0C; .NET4.0E; ms-office; MSOffice 14)
When this value of the Header named User-Agent?
- Simon_Blakely
Employee
I don't really understand your question.
- MSZ
Nimbostratus
Let me explain you. This header is getting Blocked due to ASD "Automated Client Access" ms-office. I need to know why this is occruing ? What device is using by Client? Do I need to tune my Policy to allow this ASD?
Please
- NiHo_202842
Cirrostratus
You are very unclear, but to answer your question..
When Office software downloads a file, it checks the origin (which is described in the file when downloaded) for any changes. While doing this, it uses the User-Agent header you mentioned.
- Simon_Blakely
Employee
As noted in another answer, this indicates a request that originates from Microsoft Office. For some sites (such as Sharepoint), this may be an entirely valid request.
You can disable the specific signatures that detect this for the policy
200021137 Automated client access "ms-office"
Recent Discussions
Related Content
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com