javascript - Cookie is set twice; how to remove the duplicate? -

-

so have website uses cookie remember current layout state across visits. working great until added facebook 'like' button site generates links allow users share ui state (a little confusing not relevant problem).

the problem when visit site via 1 of these facebook links second copy of layout cookie seems created (as in, see 2 cookies same name , different values). wouldn't terrible except value of duplicate cookie appears stuck, coupled fact when user returns site browser remembers stuck value instead of set value (so it's kind of there's "good" cookie can still work with, , "bad" 1 cannot, , browser likes remember "bad" cookie instead of "good" cookie). breaks layout tracking/remembering functionality.

so there 2 questions here:

  1. how stop happening/why happening in first place?
  2. how fix things users have stuck cookie (i know pick new name cookie, i'd rather finding way unstick stuck cookie)?

if use chrome's developer console after visiting page in stuck state, can see document.cookie (formatting added readability):

layoutstate=[{'id':6,'x':8,'y':1525,'z':4,'url':'undefined'}, {'id':1,'x':625,'y':709,'z':2,'url':'undefined'}, {'id':2,'x':8,'y':37,'z':3,'url':'undefined'}, {'id':3,'x':625,'y':1179,'z':5,'url':'undefined'}, {'id':4,'x':626,'y':37,'z':1,'url':'undefined'}, {'id':5,'x':626,'y':357,'z':1000000,'url':'http://m.xkcd.com/303/'}];  wibiyanotification1=1;  wibiyanotification213286=213286;  wibiyanotification213289=213289; wibiya756904_unique_user=1;  jsessionid=donthijackmeplease;  wibiyaprofile={"toolbar":{"stat":"max"},"apps":{"openapps":{}},"connectusernetworks":[null,null,null,null,null,null]};  wibiyaloads=59;  layoutstate=[{'id':6,'x':8,'y':1525,'z':4,'url':'undefined'}, {'id':1,'x':625,'y':709,'z':2,'url':'undefined'}, {'id':2,'x':8,'y':37,'z':3,'url':'undefined'}, {'id':3,'x':625,'y':1179,'z':5,'url':'undefined'}, {'id':4,'x':626,'y':37,'z':1,'url':'undefined'}, {'id':5,'x':626,'y':357,'z':6,'url':'http://m.xkcd.com/303/'}]"

ignore wibiya cookies , jsessionid. stuck cookie first 'layoutstate' instance, , 1 can still manipulate in javascript second 'layoutstate' instance. here if change things around:

layoutstate=[{'id':6,'x':8,'y':1525,'z':4,'url':'undefined'}, {'id':1,'x':625,'y':709,'z':2,'url':'undefined'}, {'id':2,'x':8,'y':37,'z':3,'url':'undefined'}, {'id':3,'x':625,'y':1179,'z':5,'url':'undefined'}, {'id':4,'x':626,'y':37,'z':1,'url':'undefined'}, {'id':5,'x':626,'y':357,'z':1000000,'url':'http://m.xkcd.com/303/'}];  wibiyanotification1=1; wibiyanotification213286=213286;  wibiyanotification213289=213289;  wibiya756904_unique_user=1;  jsessionid=donthijackmeplease;  wibiyaprofile={"toolbar":{"stat":"max"},"apps":{"openapps":{}},"connectusernetworks":[null,null,null,null,null,null]};  wibiyaloads=59;  layoutstate=[{'id':1,'x':8,'y':39,'z':1000000,'url':'undefined'}]

the second 'layoutstate' has correct information want browser remember. browser remembers value of first instance.

i've tried unsetting cookie entirely, causes second instance disappear, nothing seems rid of first instance. same behavior in major browsers (chrome, firefox, ie), makes me suspect must doing fundamentally wrong here, i'm not sure is.

you can view site here. or click here access via facebook link (should generate stuck cookie). appreciated.

update:

so steps reliably reproduce error follows:

  1. visit site via facebook-style link
  2. make changes layout, , close tab.
  3. visit site via normal url.
  4. your layout initial visit should correctly remembered, change things around , refresh page. when page reloads, changes no longer remembered.

i've noticed revisiting site via facebook-style url able clear/reset stuck cookie. it's browser keeping separate cookie each url path, or something, , not allowing root page access cookie set on other url path. thought might able fix explicitly setting path=/ on cookie, no dice.

update 2:

i've found if set both path , domain of cookie different behavior in browsers:

  1. firefox - works correctly now, hooray! worked correctly once, broke, boo!
  2. chrome - no change
  3. ie - seems keeping separate cookies each url, facebook-style url remembers 1 state, , standard url remembers different state. both update correctly , independently of each other. kind of funky, still way better stuck/broken state.

dude(tte), there inconsistencies, , bug, in cookie setter.

1. make sure path , domain correctly set

the path , domain should same both clearing cookie , setting it. see code here:

document.cookie = c_name + "=; expires=fri, 31 dec 1999 23:59:59 gmt;";

and compare to:

var c_value=escape(value) + "; expires=" + exdate.toutcstring(); + "; path=/spring; domain=aroth.no-ip.org";

you see setter has both of them, deleter doesn't. bring chaos.

2. oh, , nasty semicolon

that second line of code quoted above, has semicolon introduced in middle of string concatenation expression. right after exdate.toutcstring(). kill it. kill it…now.

at least on google chrome, managed run correctly, if set breakpoint @ json = "[" + json + "]"; , modify setcookie before executed.

p/s: bizzare debugging experience, managed set 4 layoutstate cookies, fiddling path & domain.


Comments

Post a Comment

Popular posts from this blog

php - What is the difference between $_SERVER['PATH_INFO'] and $_SERVER['ORIG_PATH_INFO']? -

-
what’s difference between $_server['path_info'] , $_server['orig_path_info'] ? how use them? when run print_r($_server) , path_info , orig_path_info not present in array. why not? how can enable them? i have read php manual on them, still don’t understand them. the path_info variable present if invoke php script this: http://www.example.com/phpinfo.php/hello_there it's /hello_there part after .php script. if don't invoke url that, there won't $_server["path_info"] environment variable. the porig_ prefix uncommon. path_info standard cgi-environment variable, , should never prefixed. did read that? (there issues around php3/php4 if invoked php interpreter via cgi-bin/ - hardly has such setups today.) for reference: http://www.ietf.org/rfc/rfc3875
Read more

fortran - Function return type mismatch -

-
i'm attempting recode old c++ program in fortran make use of lapack (i'm aware c++ have lapack++, i'm having lot of trouble installing it, gave up). i didn't have problems compilation, when had variables declared real . when started coding section of program required lapack, found parameters passed dsyev need double precision . tried change double precision (including changing hard coded numbers double precision counterparts, i.e. 0.0 -> 0.0d0) when try compile, following error of functions , subroutines i've written: error: return type mismatch of function <function> @ (1) (real(4)/real(8)) i'm not sure coming from, in program has been changed double precision. for example, i've declared following: double precision :: alpha(3),d(3),zeta1,zeta2 double precision :: a1(3),a2(3),d1(3),d2(3) double precision :: pi pi = 3.14159265359d0 alpha = (/0.109818d0, 0.405771d0, 2.22766d0/) d = (/0.444635d0, 0.535328d0, 0.154329d0 /) 10 i=1,3 ...
Read more

queue - mq_receive: message too long -

-
i implementing communication between 2 processes using queue. problem when call function mq_receive, error: message long. i have done following: struct mq_attr attr; long size = attr.mq_msgsize; .... // initializing queue "/gateway" int rc = mq_receive(gateway, buffer, size, &prio); if print size value, size=1, while when print same size program (got same mechanism), not long integer ( -1217186280 )... how can solve error?....so while size = 1, believe it's right "message long" why 1? p.s. have tried put : int rc = mq_receive(gateway, buffer, sizeof(buffer), &prio); but no result. it seems need read docs more carefully. when call mq_receive should pass size of destination buffer. this size must greater mq_msgsize attribute of queue . in addition, seems have error in queue attributes initialisation makes proper mq_receive call impossible. here standard message queue session: fill mq_attr struct ( doc ): struct mq_a...
Read more