On Sat, Dec 05, 1998, Jean Meloche wrote:
> I got a user who says:
>
> > We are running Novell's BorderManager to control user access to the
> > internet, and I can't seem to set up correct rights to a https (secure
> > address) as the main page. I would like to know if there is a link page
> > prior to your site's main page?. I know this would work as we also use
> > BCOnline and link to a page prior to the sign on page which is a https
> > type page.
>
> Is there an inherent problem with using mod_sll from behind a firewall
> or is there a configuration problem somewhere?
No, usually all you have to do on a Firewall is to allow remote ports 443
(HTTPS) to be accessible by your Intranet clients in addition to port 80
(HTTP). There is only one exception: There are some Firewalls out there who
provide a content filter for HTTP and some Firewall admins enable this filter
for both the HTTP and HTTPS remote port connections. Obviously for the HTTPS
connection this cannot work this way such easily. So the Firewall admin
should make sure this BorderManager box doesn't try such things.
Ralf S. Engelschall
[EMAIL PROTECTED]
www.engelschall.com
______________________________________________________________________
Apache Interface to SSLeay (mod_ssl) www.engelschall.com/sw/mod_ssl/
Official Support Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
