Well, you are right and so am I. The standard ports are handled, but non
standard ports have the port written to the cookie. I was using port 81 for
something and it screwed me completely. I found no solution to this
problem.
DC
----- Original Message -----
From: <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Monday, August 28, 2000 14:47
Subject: Re: SSL and Netscape
> In a message dated 8/28/00 10:36:45 AM Eastern Daylight Time,
> [EMAIL PROTECTED] writes:
>
> << Netscape establishes the cookies for a site based on the port, so
> when you
> move between one port and another the cookies set for CFID/CFTOKEN
> which
> enable session tracking change. I have recently ran into this and
> wound up
> beating my head against the wall. There is no solution that I am aware
> of.
> >>
>
> No ... because with Netscape I change from port 80 to port 443 (standard
> SSL)
> and everything works fine. However, when I change from port 80 to port
> 444
> ... well things go to hell in a handbasket?
> ------------------------------------------------------------------------
> ------
> Archives: http://www.mail-archive.com/cf-talk@houseoffusion.com/
> To Unsubscribe visit
> http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/cf_talk
> or send a message to [EMAIL PROTECTED] with
> 'unsubscribe' in the body.
>
------------------------------------------------------------------------------
Archives: http://www.mail-archive.com/cf-talk@houseoffusion.com/
To Unsubscribe visit
http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/cf_talk or send a
message to [EMAIL PROTECTED] with 'unsubscribe' in the body.
