> It seems then that I assumed too much. I figured if CF
> writes it, then CF should have access to all of it. If the
> client sends the cookie back with every http request, CF
> should have a way of accessing the cookie's attributes.
The client doesn't send everything back - it only returns the name and
value - so that's all you can see from CF. Here's a sample HTTP request
header from my browser, as seen through a nifty little Perl proxy script:
--> C06 --> S07 GET /figleafhome/images/menu_right.GIF HTTP/1.1
--> C06 --> S07 Accept: */*
--> C06 --> S07 Referer:
http://localhost:8080/figleafhome/menu.cfm?location=1
--> C06 --> S07 Accept-Language: en-us
--> C06 --> S07 Accept-Encoding: gzip, deflate
--> C06 --> S07 User-Agent: Mozilla/4.0 (compatible; MSIE 5.01; Windows NT
5.0)
--> C06 --> S07 Host: localhost:8080
--> C06 --> S07 Connection: Keep-Alive
--> C06 --> S07 Cookie: CLIENT_ID=1; CFID=99367; CFTOKEN=28414731
--> C06 --> S07 ==== Body was 0 bytes
You'll notice that there's a single header, Cookie, which lists name-value
pairs. That's all the browser sends back to the server.
On a slightly off-topic note, you can see that it's valuable at times to be
able to see and understand what's going on "under the HTTP covers". The Perl
script I used for this example lets you do this very easily, and it's
available at http://www.compansr.demon.co.uk/. Enjoy!
Dave Watts, CTO, Fig Leaf Software
http://www.figleaf.com/
voice: (202) 797-5496
fax: (202) 797-5444
------------------------------------------------------------------------------
Archives: http://www.eGroups.com/list/cf-talk
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.
