http://livedocs.adobe.com/ Macromedia LiveDocs - online documentation with user feedback. Copyright 2009, Macromedia, Inc. 2009-11-25T18:40:15 en-us http://livedocs.adobe.com/coldfusion/7/htmldocs/00000217.htm#53623 Confirmed here as well. We were getting "500 null" errors that were seemingly random across our 11-server application cluster. After some digging and testing and debugging, I managed to determine that the "500 null" error was only occuring when a user logged out of our application. In picking apart the logout() function, I realized we were also utilizing structClear(client) as well as structClear(cookie) to wipe out the user's client variables. When this executed, I noticed that the "500 null" errors would begin. Only way to resolve them was to restart the CF app server instance on whichever node had been corrupted by a call to this function. That behavior got me thinking that maybe something about using structClear(client) was causing issues with ColdFusion. That's then I found this set of comments, made th recommended change of adding a "client.hitcount=1;" after clearing the client struct, and our "500 null" errors have now completely vanished!<br /><br />Adobe, PLEASE note this as a bug and correct this behavior in the next updater.<br /><br />Tyson Vanek *** Tyson *** 0 0 2006-09-29T16:47:47 http://livedocs.adobe.com/coldfusion/7/htmldocs/00000217.htm#42221 I've been pulling my hair out because of the problem with "500 null" displaying. I have an application where I use structclear(client) on logout. I simply added <cfset client.hitcount = 1> after the StructClear, and problem was solved. Holger L 0 0 2005-11-12T07:06:52 http://livedocs.adobe.com/coldfusion/7/htmldocs/00000217.htm#40225 A follow up to my last post, if you enable client management, and then somehow delete the #client.hitCount# variable (for example by doing #structDelete( client )#) then the client data will fail to persist whenever changes are made!<br /><br />This error wont through an exception, it wont log the error, it will simply append a snippet of html to the output with "500 null"<br /><br />Any other built in client variable can be removed except for HitCount, so be careful. yoinky 0 0 2005-09-30T01:04:49 http://livedocs.adobe.com/coldfusion/7/htmldocs/00000217.htm#40086 HUGE Pain-In-The-Ass Solution:<br /><br />DO NOT USE HYPHEN CHARACTERS IN THE NAME="" ATTRIBUTE!<br /><br />Just incase you are pulling your hair out wondering why your client management isn't working (like I've been doing for the past week) and have gone through everything and can't get it working on a database or in the registry, head this very simple "rule" left out of the documentation.<br /><br />if you do use a hyphen, at the end of the request when the client scope is supposed to be automatically persisted by the runtime, it will display a "500 NULL" error in html at the bottom of the page, it won't even throw a real exception or log the error, so you have no idea it happened. yoinky 0 0 2005-09-28T02:03:13 http://livedocs.adobe.com/coldfusion/7/htmldocs/00000217.htm#36799 You should note that (in CF7 at least) the name attribute is case sensitive. Robin Hilliard 0 0 2005-07-07T01:04:15 http://livedocs.adobe.com/coldfusion/7/htmldocs/00000217.htm#33492 FYI - scriptprotect does not filter out all possible XSS attacks<br />" The scriptprotect attribute is meant to supplement to best-coding practices;<br />it provides an easy way to filter out certain tag names, but is not meant to<br />be a comprehensive solution against XSS attempts." pete_freitag 0 0 2005-05-17T09:55:01