Forum Discussion

Nikoolayy1's avatar
Nikoolayy1
Icon for MVP rankMVP

An option is to test log the variables session.client.app_id and session.client.app_version to the APM log with the Logging Agent action in the access policy:

 

 

https://support.f5.com/csp/article/K11253

 

 

But I have not tested this myself to log those exact variables, so keep that in mind.

 

 

boneyard's avatar
boneyard
Icon for MVP rankMVP
Mar 22, 2021

checked both on a tmos 14 system, first says edge, second says none.

 

there is a session.client.version also, which is 2.0.

 

seems like the host header still seems the best way.

  • Miguel_1400's avatar
    Miguel_1400
    Icon for Nimbostratus rankNimbostratus
    Mar 23, 2021

    Hi,

    thank you for comment, yes I m sure the version doesn't appear, I get -> Version: none 

    Updating client info - Hostname: XXXX Type: edge Version: none Platform: Win10 CPU: WOW64 UI Mode: Standalone Javascript Support: 1 ActiveX Support: 1 Plugin Support: 0 Model: Platform Version: Serial Number: IMEI:

    So I need to add the variables sessions session.client.app_id or session.client.app_version to get the version ?

    Regards,

  • Nikoolayy1's avatar
    Nikoolayy1
    Icon for MVP rankMVP
    Mar 23, 2021

    Try with session.client.app_version or session.client.version as boneyard said to see what you get. Also you may open a TAC case to ask why the F5 Edge Client version is not in the HTTP headers. I found only this bug in the bug tracker:

     

     

    https://cdn.f5.com/product/bugtracker/ID936061.html

  • Miguel_1400's avatar
    Miguel_1400
    Icon for Nimbostratus rankNimbostratus
    Mar 23, 2021

    Hi,

    Thank you it's work perfectly with the iRule, strange that I need to set the user-agent Header with an iRule.

     

    Regards