placing swf on asp page -- weird error

[hangalot]

Hi All

I place this problem here since I reckon I am overlooking something simple..

I have a swf that posts a xml tree to a .asp page. that works fine in testing, and even when i call the swf directly on the server.

but the minute i place the swf on a html/asp page a error gets generated with the xml i post!!

any ideas?

;)

[fgf]

need to post errors before we can offer any opinion

There are numerous ways that set up can go wrong.

(doing flash xml php at minute and it breaks often when you move stuff about)

fgf

[hangalot]

the issue at hand is as follows. I post to a asp page using xml.sendAndLoad, this returns an error in flash, i notice this by checking the return DOM's properties..., but when calling the asp page itself it returns no error. So I assumed it was a pathing problem, went bavk to my code, and decided for now to hard code the url "http://......" this did not work either... so i decided to run the swf in the browser directly, just to c what happens, and this in turn works perfectly....

so any ideas whatsoever would be much appreciated....

[fgf]

flash from the player always gets variables

in the browser it will post

this would f up xml.send etc as they send data as raw post

if your asp needs post variables then it willl only get them from the browser run version

solution always test in browser. Which is best anyway.

fgf

[hangalot]

i think what you mean by a raw post is that apart from the headers. the data in the packet is just xml, not the normal value pair system. this is fine, since it can be retrieved by just going request.form without the array tag,
i am returning valid xml as well, since i just response.write the tags and can test that by just calling the page.

it is just a stupid error, i made , prob a typo somewhere, and will have to take the time go through everything.

:( mourn --
still funny that the page is called directly as a swf on the url, whilst when hosted on a htm page in the same directory -- and then not working with an xplicit url given...