On 0, [EMAIL PROTECTED] wrote: > Tom, > > Thanks for replying. > > tc> Ahem. You do mean 'lynx https://<domain_name>/', don't you? > > Sorry to say, but yes, I did try "lynx http://<domain_name>/". > Only now do I grasp that apache-ssl does not support http. > Seems plausible for it to support http as a special case.
You can configure apache-ssl to support http and apache to support
ssl, but see below.
> tc> Trying to connect on http will not work (it uses a different
> port, 80 instead of 443 for https).
>
> I recall the mention of port numbers in the documentation
> but not the restriction to https. Of course, this is all
> painfully obvious to someone familiar with the
> correspondence between port numbers and protocols.
The association between protocols and ports is not enforced; you can
start a https server on any port you want (8443 is popular, for
instance).
> Oberon does not yet support https so my solution will
> be to toss apache-ssl and install apache.
The apache and apache-ssl packages will run quite happily side by
side, but whether you want this or not depends on what you are trying
to acheive.
Tom
--
Tom Cook
Information Technology Services, The University of Adelaide
"That you're not paranoid does not mean they're not out to get you."
- Robert Waldner
Get my GPG public key:
https://pinky.its.adelaide.edu.au/~tkcook/tom.cook-at-adelaide.edu.au
pgp7ytkeiKusL.pgp
Description: PGP signature
