dataType of "cookie" in "show stat" is string, not u64 about go-haproxy HOT 2 OPEN

Here is an example of stat dta
# pxname,svname,qcur,qmax,scur,smax,slim,stot,bin,bout,dreq,dresp,ereq,econ,eresp,wretr,wredis,status,weight,act,bck,chkfail,chkdown,lastchg,downtime,qlimit,pid,iid,sid,throttle,lbtot,tracked,type,rate,rate_lim,rate_max,check_status,check_code,check_duration,hrsp_1xx,hrsp_2xx,hrsp_3xx,hrsp_4xx,hrsp_5xx,hrsp_other,hanafail,req_rate,req_rate_max,req_tot,cli_abrt,srv_abrt,comp_in,comp_out,comp_byp,comp_rsp,lastsess,last_chk,last_agt,qtime,ctime,rtime,ttime,agent_status,agent_code,agent_duration,check_desc,agent_desc,check_rise,check_fall,check_health,agent_rise,agent_fall,agent_health,addr,cookie,mode,algo,conn_rate,conn_rate_max,conn_tot,intercepted,dcon,dses,wrew,connect,reuse,cache_lookups,cache_hits,srv_icur,src_ilim,qtime_max,ctime_max,rtime_max,ttime_max, 42ef2f50199945eb85b9c5eae7c3c656,FRONTEND,,,0,0,2000000,0,0,0,0,0,0,,,,,OPEN,,,,,,,,,1,2,0,,,,0,0,0,0,,,,0,0,0,0,0,0,,0,0,0,,,0,0,0,0,,,,,,,,,,,,,,,,,,,,,http,,0,0,0,0,0,0,0,,,0,0,,,,,,, default-42ef2f50199945eb85b9c5eae7c3c656,nic-192.168.4.118,0,0,0,0,,0,0,0,,0,,0,0,0,0,UP,1,1,0,0,0,923,0,,1,3,1,,0,,2,0,,0,L4OK,,0,0,0,0,0,0,0,,,,,0,0,,,,,-1,,,0,0,0,0,,,,Layer4 check passed,,2,2,3,,,,192.168.4.118:8080,192.168.4.118,http,,,,,,,,0,0,0,,,0,,0,0,0,0, ####192.168.4.118 is cookie value default-42ef2f50199945eb85b9c5eae7c3c656,BACKEND,0,0,0,0,200000,0,0,0,0,0,,0,0,0,0,UP,1,1,0,,0,923,0,,1,3,0,,0,,1,0,,0,,,,0,0,0,0,0,0,,,,0,0,0,0,0,0,0,-1,,,0,0,0,0,,,,,,,,,,,,,zstack_cookie,http,roundrobin,,,,,,,0,0,0,0,0,,,0,0,0,0,

from go-haproxy.

according to the haproxy doc
[cookie](https://www.haproxy.com/documentation/haproxy-configuration-manual/latest/#5.2-cookie) <value> The "[cookie](https://www.haproxy.com/documentation/haproxy-configuration-manual/latest/#)" parameter sets the cookie value assigned to the server to <value>. This value will be checked in incoming requests, and the first operational server possessing the same value will be selected. In return, in cookie insertion or rewrite modes, this value will be assigned to the cookie sent to the client. There is nothing wrong in having several servers sharing the same cookie value, and it is in fact somewhat common between normal and backup servers. See also the "[cookie](https://www.haproxy.com/documentation/haproxy-configuration-manual/latest/#)" keyword in backend section.

it doesn't mean cookie must be a interger value.

from go-haproxy.