Ajax Debugging Tip
Rey Bango posted a nice entry to help debug Ajax calls. The problem people usually run into is that Ajax triggers a remote call in the background and they have no idea to see why it failed. ajaxCFC will show you the ColdFusion error, if any, but if the problem breaks to communication for some reason it will just say invalid reply from the server... but why?! I always tell people to install a nice http sniffer, and Rey confirms it.
The moral of the story is: use Firefox, use FireBug.
The moral of the story is: use Firefox, use FireBug.
TrackBacks
There are no trackbacks for this entry.
Trackback URL for this entry:
http://www.robgonda.com/blog/trackback.cfm?40F331AD-3048-7431-E49421B012FAD62C
http://www.robgonda.com/blog/trackback.cfm?40F331AD-3048-7431-E49421B012FAD62C
Comments
[Add Comment]
Another way to trouble shoot your Ajax to CF connection is to use your CFTrace to check that the variables you passed are getting to your function, and what those values are when recieved. Look in your CFTrace log to view them.
# Posted By Laurence Hoess
| 8/24/06 7:40 PM
Thanks for link back Rob and I really appreciate the heads up about FireBug's http sniffer. Very cool.
# Posted By Rey Bango
| 8/25/06 4:55 PM
Hey has anyone used ajaxCFC with Bluedragon.net ? Its not loading for me even on the simple examples, and im in the middle of converting a server
# Posted By Jeff
| 8/28/06 9:59 AM
Still working on it Jeff; We sent New Atlanta some logs, so maybe we'll have an answer soon.
# Posted By Rob Gonda
| 8/30/06 10:46 PM
[Add Comment]
