The problem was indeed the absence of an SSL service because I was using the incorrect port. The service was running 443.
I was so concerned about potential framework incompatibilities, that I developed tunnel vision and saw only that class of problem. The WO5.4 app now works fine on a Tiger, WO5.3 deployment. I presume this means that the interface between the WOTask daemon and application instances hasn¹t changed. Good. Many thanks to the quick eyes of Simon McLean and Paul Lynch. Michael Scott On 28/07/08 4:33 PM, "Paul Lynch" <[EMAIL PROTECTED]> wrote: > As Simon says, plus see below. > > Paul > > On 28 Jul 2008, at 07:09, Michael Scott wrote: > >> I have an app developed on a Leopard box in WO5.4 and then deployed on a >> Tiger server. In deployment, the WO5.4 frameworks are bundled into the >> application package, so (I hope) the application uses nothing on the Tiger >> system. (The application doesn't use Wonder.) >> >> The deployed application works perfectly on Tiger - about which I am >> impressed - all of the functionality is just fine. Things only go wrong when >> I turn on SSL. >> >> The point at which problems occur is the redirect from the application's url >> (http://gamp.murdoch.edu.au/cgi-bin/WebObjects/CASE.woa) to the SSL based >> login page. The browser reports: >> >> Safari can¹t open the page >> ³https://gamp.murdoch.edu.au:433/cgi-bin/WebObjects/Cafe.woa/wa/Login/startLo >> gin² because it could not connect to the server ³gamp.murdoch.edu.au². > > HTTPS is usually on port 443. > >> This corresponds to what I see in debug traces. In the default Direct >> Action, I create a WORedirect component, set its URL to the startLogin¹ >> action (see above) and then return the component. After this point, nothing >> appears in the logs. I know the login page component is never instantiated, >> so presumably the problem is in the redirect to an SSL address. Also, >> dispatchRequest() on the application object is never called after returning >> the WORedirect page. >> >> The identical code in other applications works fine when deployed as WO5.3 >> on the Tiger server. >> >> Does anyone know if WO5.4 handles SSL in some different way. (Do I need to >> call 'secureMode(true)' on the WOContext.) >> >> Are there any suggestion for how I might debug this problem? >> (Unfortunately, I don't have access to a Leopard server with SSL.) I did >> turned on all the debug flags, but still there is silence after attempting to >> return the WORedirect page. > >
_______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to [EMAIL PROTECTED]
