Re:Ask HN: Why does Google put the query in the URL hash ins...
by lucb1e on Monday January 09, 2017 @03:11AM
(#13354802)
Well sure they can, how do you think the search results for "alice" are obtained? It gets sent to the server, just not upon first load but using Javascript. This Javascript could check for another query being present in the query string, or (less reliably) the server could in the referrer.
[ Parent
| on HN ]
Re:Ask HN: Why does Google put the query in the URL hash ins...
by comboy on Monday January 09, 2017 @05:32AM
(#13355343)
Why all the downvotes? I think he means that it could prevent the alice query, not the wonderland.
Re:Ask HN: Why does Google put the query in the URL hash ins...
by baby on Monday January 09, 2017 @04:56AM
(#13355222)
the server doesn't have access to anything following the hashtag. This is only accessible on the client side via javascript. Javascript that you do not have unless the browser send the first request.
Re:Ask HN: Why does Google put the query in the URL hash ins...
by lucb1e on Monday January 09, 2017 @07:11AM
(#13355747)
That's what I said:
> how do you think the search results for "alice" are obtained? It gets sent to the server, just not upon first load but using Javascript.
Re:Ask HN: Why does Google put the query in the URL hash ins...
by qeternity on Monday January 09, 2017 @05:00AM
(#13355237)
Where do you think the initial js comes from? The "wonderland" query.
Re:Ask HN: Why does Google put the query in the URL hash ins...
by lucb1e on Monday January 09, 2017 @07:12AM
(#13355753)
I know but the comment I was responding to said Google couldn't possibly know about the duplicate parameter. Well, here you have it, they can. Not at first, but still before displaying the results.