fred,
ahh yes, cross domain checking ... funny how that one caught me out ...
I've been teaching myself web app technology recently (mainly been java 'fat client' or server process developer in the past) and didn't read about the cross domain security at first.
And to begin with I was testing my html/javascript by loading it directly into the browser from the local file system (ie file:///Users/blah rather than html://localhostblah) ... which seems to allow you to then use XMLHttpRequest to call any domain you like.
So of course I wrote a whole bunch of stuff directly calling the various betfair .do scripts. Lovely.
Then I took the next step so I could get a bit more sophisticated and write my own servlets. I installed glassfish and bundled my web app and deployed it.
Then when I tested the same stuff from http:/localhost:8080/myWebApp it stopped working!!!!!
Took me a while to figure out what was going on and was pretty p1ssed off when I realised, thinking I'd wasted all my time!
However as a workaround what I've done is write a few servlets of my own which act as a proxy to betfair. So i can call https://localhost:8080/myWebApp/account/loginAction.do for example.
Not as big a pain as it sounds as the proxy servlet is very simple, but it obviously adds an extra couple of network hops into the equation so won't be using it for critical apps!
Must admit I'm quite enjoying dabbling with webapp development. You can get some quite nifty stuff running quickly using AJAX techniques.
Ok, I'm in a generous mood so I'll drop a couple of useful links in:
http://www.prototypejs.org
http://https://glassfish.dev.java.net