in both cases the server is acting the same, and what goes
over the wire is the same.
After months of seeing this problem I've finally shown
conclusively that the URLLoader ioError happens if a Timer is
running when the urlloader.load() call is made. I.E. if a Timer
happens to be running then url load fails; if no Timer is running
then url load succeeds.
Is there a known conflict between URLLoader and Timer that
would case error #2302 just because a timer is set?
I don't think there is any connection between URLLoader and a
Timer unless of course, you are able to produce a short sample code
that can reproduce the problem.
IO Error 2032 error comes in the case of any HTTP error as
the browser does not report the correct HTTP status back to the
flash player. One thing for you to try out would be to sniff the
data being passed between your app and the server using something
like Wireshark till you get the IOError. Then see what the exact
response from the server is.