Hello,
I must be missing something obvious here, but unfortunately, I cannot seem to
figure it out. I am trying my hand at developing my first Flash Remoting
project, so I am rather new to this.
When I designate the default Gateway URL to something like,
"http://www.domain.com/flashservices/gateway", all works fine if I call the
project in a browser using www.domain.com. However, if I try calling it by just
using domain.com, it does not work. Since our visitors may enter the site by
either www.domain.com or domain.com, it needs to work either way, but for the
life of me, I don't know what the workaround is (if there IS one, and if there
isn't, I guess Flash Remoting would be pretty useless for me). Any thoughts
greatly appreciated!
Thank you! Tam
atastec - 30 Dec 2005 14:20 GMT
Hi Tam,
I am extremely new to this as well, and am having problems getting flash
remoting to work for me.
Isn't your connection to the gateway hard coded into the flash file so that it
wouldn't matter what the user types into their address bar? So if they went to
http://domain.com/ it wouldn't matter because
http://www.domain.com/flashservices/gateway would still be used as the default
gateway url since that's what you have in the action script code. Does that
make sense?
I'm new to this like I said and can't even get the sample files to work so I
could be completely wrong here, but that's what it seems like to me.
Hope that helps!
Irving
Tam23 - 30 Dec 2005 17:06 GMT
Hi Irving,
Yes, the gateway is hard-coded into the actionscript of the Flash file, but
when the calling URL domain does not match the domain designated in the default
gateway (www vs. no www and visa versa), it does not work properly. A Flash
security message pops up, stating that, "domain.com is attempting to read from
www.domain.com. This is a potentially insecure operation. Do you want to allow
it?" Clicking Allow will then run the page, but this message is really
unacceptable for our visitors to see. Being new to Flash Remoting, I really
just have no idea why this occurs, and maybe I am simply missing an obvious
workaround, but I have searched and can't seem to find info on this. Does this
only happen with my system??
Anyway, I am hoping that someone will be able to share some info on this, if
only to state that, yes, this is the way it works and there is no workaround. I
will know then to abandon Flash Remoting and pursue another solution. Good luck
with your Flash Remoting endeavors, as well, Irving.
Tam
atastec - 30 Dec 2005 18:17 GMT
I should've known that would be too easy :)