Comment on Google search parameters in 2012Comments−TazeTSchnitzel14yIt irritates me that all this stuff is sent in the URL. Personally, I would put the query (and query-related) things in the URL, then use POST parameters for the stuff that the user needn't see.−mthq14yWell that would break back and forward history navigation as browsers require you te explicitly resend POST parameters.−VMG14yAlso the possibility to bookmark and to send a link to somebody else.Also after all, you want to GET the search result, not POST anything.−madrona14yWhat's the harm of sending it in the URL? That it looks a little uglier? Using POST instead of GET defeats bookmarking or linking ability.
Comments
It irritates me that all this stuff is sent in the URL. Personally, I would put the query (and query-related) things in the URL, then use POST parameters for the stuff that the user needn't see.
Well that would break back and forward history navigation as browsers require you te explicitly resend POST parameters.
Also the possibility to bookmark and to send a link to somebody else.
Also after all, you want to GET the search result, not POST anything.
What's the harm of sending it in the URL? That it looks a little uglier? Using POST instead of GET defeats bookmarking or linking ability.