lynx-dev
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

LYNX-DEV 27bugfixes update


From: Foteos Macrides
Subject: LYNX-DEV 27bugfixes update
Date: Tue, 25 Feb 1997 16:50:23 -0500 (EST)

        An updated 27bugfixes.zip is available in:
        
        http://www.slcc.edu/lynx/fote/

1997-02-25
* More reverse engineering to cope with Netscape's bogus cookie header
  parsing.  The parser must not require an '=' between the expires
  attribute name and value, because Set-Cookie headers are being
  transmitted without it (e.g., by http://law.agps.gov.au).  So Lynx
  now treats that as another special case. - FM
* Cope with invalid use of expires attributes in Version 1 cookies.
  An -06 State Management draft recommends that for "backward
  compatibility", and has been severely criticized in the HTTP-WG,
  but it would be foolish not to assume Netscape will do that.  See the
  expanded comments in LYSetCookie() of LYCookie.c for more information.
  Note that "expires" thus cannot be used as a Version 1 cookie name, but
  a provider would be foolish to use that, anyway.  Note also that the
  possibility of using different header names for Version 1 versus
  Version 0 (a.k.a., "Netscape") cookies is being discussed in the
  HTTP-WG, which might have been better to do in the first place, but
  the -05 draft has been approved as RFC 2109:
    http://info.internet.isi.edu/in-notes/rfc/files/rfc2109.txt
  so it would be a while before that were done, if ever. - FM


                                Fote

=========================================================================
 Foteos Macrides            Worcester Foundation for Biomedical Research
 address@hidden         222 Maple Avenue, Shrewsbury, MA 01545
=========================================================================
;
; To UNSUBSCRIBE:  Send a mail message to address@hidden
;                  with "unsubscribe lynx-dev" (without the
;                  quotation marks) on a line by itself.
;

reply via email to

[Prev in Thread] Current Thread [Next in Thread]