Folks-

If you follow my solution above, and run the example script, you can see the cookies path, name, and value in the output.

However many of the values are now encrypted. HTTP::Cookies::Chrome claims to know how to decode them by finding a password in my keychain on Mac. However the results don't look like they've decoded properly. see update below

Any pointers are much appreciated!

Thanks

Craig

Example Output:

.33across.com
    /     33x_ps           ?C?5?T-76?Q???$?HW>...
.3lift.com
    /     tluid            ?0j???t?*??3M?("D???1?0...
    /     tluidp           ?0j???t?*??3M?("D???1?0...
.a-mo.net
    /     amuid2           ;??\????
W{??"?$?b???K?S...
    /     pamuid2          ;??\????
W{??"?$?b???K?S&...
[download]

UPDATE: Hold on there cowboy! It seems that the entries are being decoded, but with a bunch of binary poop before them.

Here is an example of a cookie that the Chrome developer shows a value of: 1af15945-c298-4041-a6e7-45b5e233cf82

.costco.com
    /     BVBRANDID        {?'}~???X???2?6%t????7T????#1af15945-c2
+98-4041-a6e7-45b5e233cf82
[download]

Anybody know what that stuff is before the hash?

Thanks

Craig