_GPSLSC cookie size grows too big with Magento

[icarinix]

Just experienced an issue on a client site where the _GPSLSC cookie grew too large and resulted in Apache rejecting the request (Error 400) because the request headers were too large.

I've seen one other report of this happening on stackoverflow - again, a Magento site- https://magento.stackexchange.com/questions/85583/internal-server-error-because-one-cookie-is-too-big

My theory is that Magento is especially susceptible to this because of the number of javascript and css resources loaded from quite long pathnames - for example one file path generated by minify / combine CSS on my clients site at present is

/skin/frontend/XXXXX,_default,_font-awesome-4.2.0,_css,_font-awesome.min.css+XXXXX,_default,_css,_owl.css+XXXXX,_default,_css,_custom_bootstrap.css+XXXXX,_default,_css,_styles.css+XXXXX,_default,_css,_responsive.css+base,_default,_css,_widgets.css+XXXXX,_default,_advancedreviews,_css,_advancedreviews.css+base,_default,_onsale,_css,_product_onsale_label.css+base,_default,_onsale,_css,_category_onsale_label.css+base,_default,_css,_mirasvit,_helpdesk,_rwd.css+base,_default,_css,_euvat.css.pagespeed.cc.iLAXVbYm-W.css

Disabling local_storage_cache does fix this naturally, as the cookie is no longer used, but thats a bit of a shame as this could boost speed quite a bit.

[Lofesa]

Hi @icarinix

Have you tried ModPagespeedMaxSegmentLength? Ref. here

[whench18]

hello you can also try using the long path tool.