Ever wondered why Google has so long URLs? I think it’s because they have many info from variables from that URLs. For example, down I put the code from the Chrome logo (from the webpage that appears on Chrome browser when the web page doesn’t exist. What kind of information does Google collect from this kind of long URLs? And if we discuss about long URLs, you did notice the long URLs when you search something on Google.com? They collect lots of information from a URL. Do you know any of those information from Google long URLs?
#logo-img {
/* "Not allowed to load local resource: chrome://theme/IDR_PRODUCT_LOGO",
so embed the resource manually. */
content: -webkit-image-set(
url('data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAKsAAAAgCAYAAABtn4gCAAAI9klEQVR4Xu2cfYxcVRmHn3Pu3Nm6lXa2ta0AYlsgFSGgThMU0W5hGkqApNGARk3cGm3BRN3FYGuCISrBXaNphcSkG2I3hn9gY2gSNWq32AoE1C6KRihFti2QSgvsTmm783HvOa+zM69cSS8Tacsq7n2SX87cj5P7ZvLs2ztnbseICG8HMjIsbxMyMnIoxhja8fJnriuYMNdjOsIVNhd0Y0wBRbxH6nHZ16OdUot2iXNDC3/2mzJtOImOnpHJ2p4Xr13ZkDTYJLHrwRgwPJggg==') 2x);
}
That’s a base64 encoded image. It’s just the data for the chrome logo itself. Web developers sometimes embed images that way as an optimization technique. It has the advantage of saving you one HTTP request. (the HTTP headers aren’t insignificant, especially for a website that gets as much traffic as google.) Unfortunately you can’t cache embedded images, so there’s that.
As for what the long search URLs mean, most/all of those name value pairs are explained here.
The long URLs were a specific decision to allow someone to copy/paste a link of results to someone else and have them see the same thing. If they just included the search query as the URL parameter and stored everything else in POST, their localized search results would be different for everyone clicking on a link.