Forum Discussion
WAF ASP.NET_SessionId cookie not sent by the client
See https://my.f5.com/manage/s/article/K21122429
Also allow the cookie on ASM as seen in https://my.f5.com/manage/s/article/K95345460 and play with the options as maybe ASM is adding an extra flag to the cookie. Also remove the cookie if it is enforced as if the cookie is saved the client PC (not session cookie) it can't be enforced.
Outside of that open a TAC case.
- Darius44Jul 27, 2023Altocumulus
Hello,
Thank you for you answer first of all.
I don't believe the number of cookies is the problem, as the WAF only learned 10 of them and in the request sent by the client when the process is not working it is sending only the TS cookie and when it does work (after the trick with unnasign and re-assign) it send both the TS and the ASP cookie.
Thank you!
- Nikoolayy1Jul 27, 2023MVP
See the extra notes I just added but maybe it will need a TAC assistance.
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