NYCPHP Meetup

[Chris Bielanski]

The answer might very likely be an arg string not unlike a GET string,
buried in the "value" value. I'll scope the RFC again, but I can't think of
anything preventing your cookie storing
name="mycookie" value="expiry=<date-time>&foo1=bar1&foo2=bar2..."

This will allow for a handy parsing (since hey!! it's a URI!!)

Thanks,
Chris Bielanski - [CBielanski at inta.org]
Web Programmer, 
International Trademark Association - [www.inta.org]
1133 Ave. of the Americas - Manhattan
p - 212/642-1745





-----Original Message-----
From: Adam Maccabee Trachtenberg [mailto:adam at trachtenberg.com]
Sent: Tuesday, February 03, 2004 5:52 PM
To: NYPHP Talk
Cc: rahmin at insite-out.com
Subject: Re: [nycphp-talk] Fw: reading cookie expirations


On Tue, 3 Feb 2004, -sry wrote:

> In an off-list continuation, he noted, that the $HTTP_COOKIE_VARS
> array is just an array of cookies, not an array of values for *a*
> cookie. Is he right? :-( Really? :-(((( bahhhh....so how do we get
> the other stuff besides name and value? now *I* want to know!

Cookies do not return the information that you're looking for. They
only return the cookie's name and value. (And maybe the path and
domain.)

See RFC 2109 for more information:

http://www.cis.ohio-state.edu/cgi-bin/rfc/rfc2109.html

-adam

-- 
adam at trachtenberg.com
author of o'reilly's php cookbook
avoid the holiday rush, buy your copy today!
_______________________________________________
talk mailing list
talk at lists.nyphp.org
http://lists.nyphp.org/mailman/listinfo/talk