Post Reply 
proper format for cookievalues
Jun. 11, 2011, 10:36 AM
Post: #1
proper format for cookievalues
using sidki's latest and greatest.

what is the proper format for removing or modifying cookievalues?

ie.
..\Lists\sidki_l_2010-10-23\CookieValues.ptxt

some cookies can be modified with \=[^;]+ but some use format =[^;]+ and yet some use format [^;]+

what is the syntax for needing/using the backslash or equal sign ?
Add Thank You Quote this message in a reply
Jun. 12, 2011, 12:11 AM
Post: #2
RE: proper format for cookievalues
Depends on the site's headers and maybe your best guess.
A site has a tracking header 'a=youare10;' and a header 'apple=no;'. "a\=[^;]+" only matches 'a=youare10;'. "a[^;]+" matches both headers. Maybe you need 'apple=no' or don't.

As a matching character "=" matches an "=" and the spaces before and after. "\=" only matches the "=".

I see "\=[^;]+" in CookieValues.ptxt, not just "=[^;]+".

HTH
Add Thank You Quote this message in a reply
Jun. 27, 2011, 12:21 PM
Post: #3
RE: proper format for cookievalues
still using sidki's latest and greatest.

came across a cookievalue that no matter what I try, it still keeps appearing and IS NOT listed as a removed or modified cookie when I hover mouse over the cookie link on the page

could it be because the cookie name itself has a period ?

the cookie is:
adcookie.default=true
Add Thank You Quote this message in a reply
Jun. 29, 2011, 03:50 AM
Post: #4
RE: proper format for cookievalues
(Jun. 27, 2011 12:21 PM)susa Wrote:  could it be because the cookie name itself has a period ?

I don't think so (has been a long day though). How is the cookie set?

Cookies may be created by incoming set-cookie headers, javascript, meta statements.
Only the incoming header filter "Set-Cookie: 3 Filter Cookie Content" uses CookieValues.ptxt.
Modify cookies that were created by javascript or meta statements appears to require faking it.

Code:
## fake cookies                                 $SET(0=f_cookie.) $SET(sCookieF=*)

Have you tried adding something like

"URL match" $OHDR(cookie: adcookie.default[^;]+;+\9|\8; adcookie.default[^;]+\9&$SET(sCookieF=\8\9)$SET(0=f_cookie.))

to Exceptions-U?

HTH
Add Thank You Quote this message in a reply
Jun. 30, 2011, 01:15 AM
Post: #5
RE: proper format for cookievalues
>> to Exceptions-U?

added precisely as below to exceptions-u.ptxt, did not work

snagit capture from ultraedit and did a refresh of all rules before testing


Attached File(s)
.jpg  cookie.jpg (Size: 55.41 KB / Downloads: 632)
Add Thank You Quote this message in a reply
Jun. 30, 2011, 02:47 AM
Post: #6
RE: proper format for cookievalues
I think you missed the "URL match".
Add Thank You Quote this message in a reply
Jun. 30, 2011, 04:44 AM
Post: #7
RE: proper format for cookievalues
(Jun. 30, 2011 02:47 AM)whenever Wrote:  I think you missed the "URL match".

Correct but the entry could still work. It could also break and slow things down.

(Jun. 30, 2011 01:15 AM)susa Wrote:  added precisely as below to exceptions-u.ptxt, did not work

I tested it on cookie headers at yahoo. I'll probably need a address to see what is happening.
Are there any Exceptions-U blocklist matches for the address that uses the cookie?
Add Thank You Quote this message in a reply
Post Reply 


Forum Jump: