My guess is much like Tim Healt's. If you're calling a web service like a WSDL/SOAP service, the # should be fine. If you're calling it directly via URL params, like ?method=x&argument1=v#riable, the # is a sign to your web server that the URL params stop there - it's a href hash, which goes to the browser not the server.
If that's the case, then URL encoding on the client would be necessary. The bad news is URL encoding may pass on this because # is a valid URL parameter, just not what you want. In that case, you may have to manually replace # with %23. nathan strutz [www.dopefly.com] [about.me/nathanstrutz] On Fri, Feb 7, 2014 at 12:14 PM, Adam Cameron <[email protected]> wrote: > > On 7 February 2014 18:07, Jon Clausen <[email protected]> > wrote: > > > > > Bryan, > > > > For clarification, how are the comments content being evaluated by CF and > > causing it to choke? It seems to me that those should be handled as > > strings and that they wouldn't be evaluated by CF, unless they are > wrapped > > in an eval(). > > > > Seconded. I think people are suggesting treating a symptom here, rather > than the problem. > > How is this problem of yours manifesting itself? "CF chokes on the single > pound in the variable" is not a very clear description of what's going > wrong. > > Can you pls clarify? > > -- > Adam > > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Order the Adobe Coldfusion Anthology now! http://www.amazon.com/Adobe-Coldfusion-Anthology/dp/1430272155/?tag=houseoffusion Archive: http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:357625 Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/groups/cf-talk/unsubscribe.cfm
