| Edward J. Apostol 2005-04-18, 2:45 am |
| Hi everyone -
I have a question that I hope someone can help me out with.
A few weeks ago there was a thread on SSL and Flashcom/Flash Remoting,
responded to by Brian (Lesser) - Hey Brian.
I have been instructing a number of corporate clients on development of
Flashcom-related applications to their respective developers.
In one case, they were looking for a demonstration of SSL with Flashcom in a
development environment, so this is what I did.
1. Using Win XP Pro (or 2000) and its version of IIS. Note that its NOT
win 2003 server, because we want to actually implement SSL on dev systems
(and not test it against a Win 2K3 Server OS, which I know has server cert
capabilities/SSL), so that the developers can test individually and locally.
2. I was able to set up SSL and a self-generated certificate on IIS
running on Win XP Pro and Win 2000. These dev systems are running Flashcom
dev version as well.
3. surfing to https://localhost/ reveals that SSL is working off port
443, certificate runs fine
4. surfing to https://localhost/flashservices/gateway/ works as well,
indicating that SSL is enabled over the flash remoting gateway.
5. I set up a simple client side Flash App with a username field,
password field, and a button that triggers access to the remoting gateway.
6. The username and password are passed via remoting to a CF component
for validation (and confirmation via comparing the username/password with a
database).
7. The user is either allowed to proceed or not.
In the Flash environment, when testing the sample app WITHOUT the https://
referenced in the code (and of course, under IIS and no SSL) the app runs
fine.
However, when I run it with references to the flash gateway and https://, as
in..
//initialize the Flash Remoting Object
NetServices.setDefaultGatewayUrl("https://localhost/flashservices/gateway");
I always get the non-descriptive error -
"Error opening URL https://localhost/flashservices/gateway"
No other details provided in the various debuggers.
Note I have references to the gateway and https:// on both the client side
fla and serverside Actionscript (main.asc, initiating the gateway using
Flashcomm Application's onConnect event).
But wait-a-minute.when I surf to it by itself in a web browser, I get the
classic blank window to indicate the gateway is working.
I'm confused...I can make IIS on Win XP/2000 Pro enabled with SSL, but with
Flashcom/Flash Remoting it appears to work "half way".
Any thoughts or comments are appreciated.
Regards
Edward Apostol
Developer, instructor
Web Applications, Wireless, Rich Media
Toronto, ON Canada
=-----------------------------------------------------------
Supported by Fig Leaf Software - http://www.figleaf.com
=-----------------------------------------------------------
To change your subscription options or search the archive:
http://chattyfig.figleaf.com/mailman/listinfo/flashcomm
|