Forum Discussion

Urosh's avatar
Urosh
Icon for Altostratus rankAltostratus
Jun 23, 2023

ASM not passing client cookies to the node servers

Hello everyone We're having issues when enabling ASM on the virtual server serving the Cisco Meeting Server WebRTC application. Te problem is that the users are unable to join meetings as soon as we...
application delivery
security
  • Urosh's avatar
    Urosh
    Jun 26, 2023

    The problem was resolved by enabling the websocket profile on the VS.

    Thank you all for your help and suggestions. 

CA_Valli's avatar
CA_Valli
Icon for MVP rankMVP
Jun 23, 2023

Hello,
I think you might be reading this information wrong. By design, the F5 WAF engine injects a new cookie in the client-side connection, and uses it to correlate client events within a session and to check data integrity.

So, the behavior you're seeing in the capture is correct. The full server-response that you're receiving is being forwarded as-is to the client (well, it does strip the nginx information), and the WAF uses the set-cookie attribute to create a hash for this session.

Consequent client requests to the WAF will include this hashed cookie, and since the server doesn't require to see it, it's not being forwarded. 

I'm not seeing missing informations from the logs you attached. Let me know if this is clear enough! 
KB reference for ASM cookies: https://my.f5.com/manage/s/article/K6850