From owner-freebsd-isp Fri Jan 16 01:57:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA01945 for freebsd-isp-outgoing; Fri, 16 Jan 1998 01:57:24 -0800 (PST) (envelope-from owner-freebsd-isp@FreeBSD.ORG) Received: from freefall.pipeline.ch (intranet.pipeline.ch [195.134.128.66]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA01940 for ; Fri, 16 Jan 1998 01:57:17 -0800 (PST) (envelope-from andre@pipeline.ch) Received: from pipeline.ch ([195.134.128.41]) by freefall.pipeline.ch (Netscape Mail Server v2.02) with ESMTP id AAA194 for ; Fri, 16 Jan 1998 10:22:25 +0100 Message-ID: <34BF26B8.F0071260@pipeline.ch> Date: Fri, 16 Jan 1998 10:22:00 +0100 From: "IBS / Andre Oppermann" Organization: Internet Business Solutions Ltd. (AG) X-Mailer: Mozilla 4.03 [en] (WinNT; U) MIME-Version: 1.0 To: freebsd-isp@FreeBSD.ORG Subject: Re: Distributed Webservers References: <199801160210.UAA11703@nospam.hiwaay.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org David Kelly wrote: > In the nature of WWW, with hyperlinks all over the place, we have a > customer who wants authenticated logins to all of their sites, scattered > hither and yon. On following a hyperlink to another site (part of their > system) is not happy with an additional password challenge. > > Others are working this problem, but from what I hear the supposed > solution involves purchasing everything in Netscape's catalog. > > Any suggestions? Sample code? You can use a session cookie for the whole site (*.mysite.com). This works only with Netscape Browsers. The other way is to use SSL and client auth. -- Andre Oppermann CEO / Geschaeftsfuehrer Internet Business Solutions Ltd. (AG) Hardstrasse 235, 8005 Zurich, Switzerland Fon +41 1 277 75 75 / Fax +41 1 277 75 77 http://www.pipeline.ch ibs@pipeline.ch