In article <199507241015.MAA06204@wswiop05.win.tue.nl>, Koen Holtman writes: > > However, the redirection (3xx) feature in HTTP would allow cooperating > service providers to obtain (session-id for server a.com,session-id > for server b.com) pairs where both are known (with 100% accuracy) to > originate from the same user agent. Can you explain this? I don't understand how redirection affects these issues. For example, under the Netscape scheme, if server a.com issues a redirect to server b.com the client does an entirely new request to the new server, without any session-id if b.com is not equal to a.com. Under the Netscape proposal, however, the cookie can be shared between host a.x.com and b.x.com. It cannot be shared between a.x.com and *.y.com. (This is according to the spec -- I don't know how it is currently implemented). -- John Franks Dept of Math. Northwestern University john@math.nwu.eduReceived on Monday, 24 July 1995 11:33:13 GMT
This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 27 October 2009 08:38:36 GMT