Forum Discussion
richard_77048
Jun 08, 2011Nimbostratus
Thanks for all the good tips. I now have a better idea of what is happening here.
So, I have ditched, at least temporarily, the approach of just sending the cookie to the server on the back. Instead, I set a cookie in an HTTP_RESPONSE event. Now, the browser reports the cookie as expected and sends it along. The F5 reports the existence and value of the cookie as expected.
Now, looking at the application logs the cookie that the application sees is this, for example: ", language=fr". That is "comma space langugae=fr". I am thoughtlessly removing the cookie and inserting it with the appropriate value. Where are the comma and the space coming from? Is this just a problem in the application? Is the F5 inserting the cookie like that? As I said earlier in this thread, there is a known issue detailed in the release notes for 9.4.x where a trailing semicolon gets inserted with a cookie. Could this be a similar issue?
Richard