Bug#64308: state of #64308

2011-06-02 Thread Dominic Hargreaves
On Sat, Oct 17, 2009 at 12:12:49AM +0300, Eugene V. Lyubimkin wrote:
 Joey Hess wrote:
  I don't have comprehensive knowledge of every browser. The current
  version of lynx has support for the expires field (in addition to
  Max-Age).
  
  I'd still appreciate it if perl followed the actual RFC, even if every
  browser has support for the old spec.
  
 Ok, I just forwarded the report upstream.

It might be worth pointing out here that there has been quite a
bit of work on the upstream bug report
https://rt.cpan.org/Public/Bug/Display.html?id=50576 including a
request to review an implementaion of the Max-Age support you
requested from a few months ago.

Cheers,
Dominic.

-- 
Dominic Hargreaves | http://www.larted.org.uk/~dom/
PGP key 5178E2A5 from the.earth.li (keyserver,web,email)



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#64308: state of #64308

2009-10-16 Thread Eugene V. Lyubimkin
Hello Joey,

CGI::Cookie would lead you to belive it follows RFC 2109, when it says
For full information on cookies see
http://www.ics.uci.edu/pub/ietf/http/rfc2109.txt
I wouldn't read this as 'conforms to', nevertheless:

CGI::Cookie uses only the old
expires field that is in the old netscape cookies spec.
This is still the case with Perl 5.10.1. Is it still a problem with any
browser? Should I forward upstream the request to implement 'Max-Age' now?

Note: For backward compatibility, the separator in the Cookie header
   is semi-colon (;) everywhere.  A server should also accept comma (,)
   as the separator between cookie-values for future compatibility.
This part works well for me in Perl 5.10.1.

-- 
Eugene V. Lyubimkin aka JackYF, JID: jackyf.devel(maildog)gmail.com
C++/Perl developer, Debian Developer



signature.asc
Description: OpenPGP digital signature


Bug#64308: state of #64308

2009-10-16 Thread Joey Hess
Eugene V. Lyubimkin wrote:
 CGI::Cookie would lead you to belive it follows RFC 2109, when it says
 For full information on cookies see
 http://www.ics.uci.edu/pub/ietf/http/rfc2109.txt
 I wouldn't read this as 'conforms to', nevertheless:
 
 CGI::Cookie uses only the old
 expires field that is in the old netscape cookies spec.
 This is still the case with Perl 5.10.1. Is it still a problem with any
 browser? Should I forward upstream the request to implement 'Max-Age' now?

I don't have comprehensive knowledge of every browser. The current
version of lynx has support for the expires field (in addition to
Max-Age).

I'd still appreciate it if perl followed the actual RFC, even if every
browser has support for the old spec.

-- 
see shy jo


signature.asc
Description: Digital signature


Bug#64308: state of #64308

2009-10-16 Thread Eugene V. Lyubimkin
package perl
tags 64308 + confirmed
forwarded 64308 https://rt.cpan.org/Public/Bug/Display.html?id=50576
thanks

Joey Hess wrote:
 I don't have comprehensive knowledge of every browser. The current
 version of lynx has support for the expires field (in addition to
 Max-Age).
 
 I'd still appreciate it if perl followed the actual RFC, even if every
 browser has support for the old spec.
 
Ok, I just forwarded the report upstream.

-- 
Eugene V. Lyubimkin aka JackYF, JID: jackyf.devel(maildog)gmail.com
C++/Perl developer, Debian Developer



signature.asc
Description: OpenPGP digital signature