Skip to main content
This topic has been closed for replies.

1 reply

T
tsongas
Participating Frequently
March 30, 2012

Having the secureJSONPrefix setting default to "//" instead of nothing in the CF administrator, thereby causing SerializeJSON to create invalid JSON that won't work with jQuery, is the kind of idiotic maneuver that is sending people away from Adobe ColdFusion to Railo.

12Robots
12Robots
Participating Frequently
March 30, 2012

So having a default that does nothing to secure the request is a better idea in your opinion?

If Adobe went with your idea then placing a checkmark in that box would not change a thing. The application would go on working and the admin/develop would think that now their JSON data was all safe and sound creating a false sense of security.

I think you misplaced the label "idiotic"

Perhaps you are just upset cause you didn't read the documentation first and spent some hours trying to figure out why all your Ajax calls suddenly started breaking.

Oh, and Railo uses the same default.

Jason

Terms & ConditionsAccessibility statement
Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices