▁strings ▁form ▁part ▁of ▁the ▁URL , ▁and ▁are ▁therefore ▁included ▁if ▁the ▁user ▁saves ▁or ▁sends ▁the ▁URL ▁to ▁another ▁user ; ▁cookies ▁can ▁be ▁maintained ▁across ▁brow sing ▁sessions , ▁but ▁are ▁not ▁saved ▁or ▁sent ▁with ▁the ▁URL . ▁ ▁If ▁the ▁user ▁arriv es ▁at ▁the ▁same ▁web ▁server ▁by ▁two ▁( or ▁more ) ▁independent ▁paths , ▁it ▁will ▁be ▁assigned ▁two ▁different ▁query ▁strings , ▁while ▁the ▁stored ▁cookies ▁are ▁the ▁same . ▁ ▁The ▁user ▁can ▁disable ▁cookies , ▁in ▁which ▁case ▁using ▁cookies ▁for ▁tracking ▁does ▁not ▁work . ▁However , ▁using ▁query ▁strings ▁for ▁tracking ▁should ▁work ▁in ▁all ▁situations . ▁ ▁D ifferent ▁query ▁strings ▁passed ▁by ▁different ▁vis its ▁to ▁the ▁page ▁will ▁mean ▁that ▁the ▁pages ▁are ▁never ▁served ▁from ▁the ▁browser ▁( or ▁proxy , ▁if ▁present ) ▁cache ▁thereby ▁increasing ▁the ▁load ▁on ▁the ▁web ▁server ▁and ▁slow ing ▁down ▁the ▁user ▁experience . ▁ ▁Comp at ibility ▁issues ▁ ▁According ▁to ▁the ▁HTTP ▁specification : ▁Vari ous ▁ad ▁h oc ▁limitations ▁on ▁request - line ▁length ▁are ▁found ▁in ▁practice . ▁It ▁is ▁RE CO MM EN DE D ▁that ▁all ▁HTTP ▁send ers ▁and ▁recip ients ▁support , ▁at ▁a ▁minimum , ▁request - line ▁lengths ▁of ▁ 8 0 0 0 ▁oct ets . ▁ ▁If ▁the ▁URL ▁is ▁too ▁long , ▁the ▁web ▁server ▁fails ▁with ▁the ▁ 4 1 4 ▁Request - URI ▁To o ▁Long ▁HTTP ▁status ▁code . ▁ ▁The ▁common ▁workaround