Sacrificial RabbitCode. Art. Perversion. Madness.

Thursday, January 12. 2006

Debugging Ajax

When debugging an Ajax application, especially one that is talking to a REST API, especially especially if that REST API is one of your own building.

I was getting this strange error in the JavaScript console, NS_ERROR_ILLEGAL_VALUE 80070057. Something about an uncaught exception. Well, the solution was to stop using AJAX, and get right down to brass tacks: Telnet is your friend.

telnet bunny.jonnay.net 80
Trying 142.179.114.225...
Connected to panda-ba.sanriowasteland.net.
Escape character is '^]'.
DELETE /projects/TileEditor/tiles/tile.php?tiles=43c75444b6253 HTTP/1.1
Host: bunny.jonnay.net

If you just send raw request headers through telnet, it makes it a bit easier to understand what is happening. I will bet however, that if you are getting the NS_ERROR_ILLEGAL_VALUE messages, it means that you have some errant back-end code, and your error messages are none too friendly.

Better error messages will be a feature in meditation 0.2
Posted by jonnay in Code at 23:45 | Comments (0) | Trackback (1)
Defined tags for this entry: , , , , ,

Trackbacks
Trackback specific URI for this entry

Debugging Restuful Ajax... Part Deux.
In my last entry about Debugging REST and AJAX, I talked about using telnet as an easy way to figure out WTF is going on with your application, if you have some kind of general badness. Incidentally enough, it also comes in handy when you want to quick
Weblog: Sacrificial Rabbit
Tracked: Jan 16, 00:34

Comments
Display comments as (Linear | Threaded)

No comments

Add Comment

E-Mail addresses will not be displayed and will only be used for E-Mail notifications

To prevent automated Bots from commentspamming, please enter the string you see in the image below in the appropriate input box. Your comment will only be submitted if the strings match. Please ensure that your browser supports and accepts cookies, or your comment cannot be verified correctly.
CAPTCHA