Copy link to clipboard
Copied
We are running ColdFusion 10 application server and using Omniture in our application. Since upgrading to CF 10, we have been getting the following error:
Oct 19, 2013 3:43:30 PM org.apache.tomcat.util.http.Cookies processCookieHeader
INFO: Cookies: Invalid cookie. Value not a token or quoted value
Maybe there is an easier solution to rid ourselves of this error, but this is what I've found.
I have already pinpointed the issue, which is with the format of Omniture's one cookie which contains brackets. We reached out to them about chaning that format, and they replied the couldn't and that no one else is having the issue. I have found that at least other Tomcat users are having the same issue and it had been suggested to edit a setting. So one our options for eliminating this issue is to adjust the setting in Tomcat that is bult-in to CF 10. From what I've gathered I need to add ALLOW_HTTP_SEPARATORS_IN_V0 to my configuration and set it to true. I've found configuration files for Tomcast in the CF runtime directory. And I suspect I need to add some code to server.xml.
At this point, I'm not sure how to include the setting or if I'm correct about the proper config file.
If anyone can help me resolve this issue, it will be greatly appreciated.
Marc
Copy link to clipboard
Copied
I was able to determine I had to incorrect file. If I wanteds to use the setting, it would need to be on catalina.properties file.
I did try the following lines, but that did not solve the issue:
tomcat.util.http.ServerCookie.ALLOW_HTTP_SEPARATORS_IN_V0=true
and then I tried
org.apache.tomcat.util.http.ServerCookie.ALLOW_HTTP_SEPARATORS_IN_V0=true
Either did not solve the issue after restarting CF.
So at this point I'm open to other suggestions.
Thanks,
Marc
Copy link to clipboard
Copied
i don't know how to eliminate the issue, but I can eliminate the error message. Is that of interest?
Copy link to clipboard
Copied
Yes. This will provide us with an option.
Copy link to clipboard
Copied
Find the logging.properties files for your JRE. We use JRE 7 so ours is in C:\Program Files\Java\jre7. Then look in the lib subfolder for logging.properties file and change:
to
java.util.logging.ConsoleHandler.level = SEVERE
That should get rid of the errors at least.