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, W
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
this doesn't sound like a code problem at all - more like an apache
config problem. it sounds to me like you don't have the SSL port open,
or you don't have an SSL web site configured for that domain.
first of all just make sure you can connect to https://gamp.murdoch.edu.au
i'm guessing you
Oops perhaps this belongs on the deploy list. I was thinking from the
perspective of code. I¹ll post it in the other place.
On 28/07/08 2:09 PM, "Michael Scott" <[EMAIL PROTECTED]> wrote:
> I have an app developed on a Leopard box in WO5.4 and then deployed on a Tiger
> server. In deployme
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
