7 ms·

Just my knee-jerk opinion, but absolutely not acceptable. I can't see any way in which this could be construed as "expected behavior."

dogma1138 11y ago
I don't think google search URL's were ever designed to be shared nor linked directly so I don't really see an issue here. The original query is stored in case you want to track back on the auto-suggest would you rather they to store those in cookies or non-volatile browser storage? And while it's true that if you link some one an entire Google URL search URL you might leak the original query, but given all the other dark magic that is in the URL which can include your client type, version, location and other things (e.g. inter-service referrals if you go there from another google service like Google Maps) i think the original query is the least of your worries. And if you want to link a query well just use https://www.google.co.uk/search?q=how https://www.google.co.uk/search?q=how to use google works just fine.
- simoncion 11y ago
  > I don't think google search URL's were ever designed to be shared nor linked directly... This is incredibly silly. URLs are how you get to a page. It's how The Web works! > The original query is stored in case you want to track back... That's what the History API is for. When you add an anchor-tag query, store the original state in the tab's history. > i think the original query is the least of your worries. Infoleaks are BAD. The least Google could do is use their URL rewriting powers to remove the original query when they add a query stored in the anchor-tag.
  - dogma1138 11y ago
    > This is incredibly silly. URLs are how you get to a page. It's how The Web works! That's a very general and simplistic view of things, and we both know it's not true. While URL's were designed originally to only provide an address for a specific resource we all know they are also used for storage, user state management and many other things, again not ideal but in some cases unavoidable. Not to mention that URL's are not implicitly intended to be shared outside of the scope of your application you wouldn't link the 3 mile long URL that you get every time you login into your bank account would you? > That's what the History API is for. When you add an anchor-tag query, store the original state in the tab's history. Technically (best kind of not true) not true for the Google History API and even if it would be applicable for this it doesn't work in cases where you for example weren't signed in or explicitly blocking google tracking API's and services. Not to mention that making a API call every time you need to do something as basic as backtracking on your search is just pure insanity when it comes to resourcing. And if you are talking about the Chrome Page History API then why in god's name would i want a site to access it, not to mention it's not applicable in this case either. > Infoleaks are BAD. The least Google could do is use their URL rewriting powers to remove the original query when they add a query stored in the anchor-tag. Life is bad, if this was in a link which was automatically shared (although all those pin URL generators link 10 fold more data than Google) I would agree with you, otherwise not really this isn't a use case for the application.
    - simoncion 11y ago
      > ...we both know it's not true. I know no such thing. When I want to share a search result or anything else -that doesn't require authentication- with a friend, I copy the URL in the address bar and paste it to them. This is how The Web works. > ...if this was in a link which was automatically shared... I would agree with you [that this is a bad thing.] So, it would be acceptable to you if Google put your Google Account login and password in URI-encoded plain text in the URL of your search results? Why or why not? > Not to mention that making a API call every time you need to do something as basic as backtracking on your search... 1) Google already does exactly what I described when you make a search on *.google.com with a Javascript-enabled browser. It's what lets your back button work with their JS-based page updates. ;-) 2) A person driving his User Agent doesn't use the History API to go to a previous search result. He uses his back button or equivalent key combo.
      - dogma1138 11y ago
        >This is how The Web works. This is one of many ways the web works, URLs were designed way before there was an easy way to share them outside of the scope of the website it self. Looking at my history 50-60% of the URL's in it aren't humanly readable and are 10 miles long, many of them do not require authentication it would be nice if people would adhere to URL's are meant to be humanly readable and easy to share but you know... ...life. >Google already does exactly what I described when you make a search on *.google.com with a Javascript-enabled browser. It's what lets your back button work with their JS-based page updates. ;-) No it doesn't my back button works just fine and there isn't a single request made when i click it, just tried it know both with the network parses in chrome dev tools and fiddler. And again the history API isn't used for this not to mention it has been deprecated and turned into the App Activities API which has quite a different set of functions now, moments are still supported but it's pretty weird now. https://developers.google.com/+/history/ https://developers.google.com/+/history/ https://developers.google.com/+/features/app-activities https://developers.google.com/+/features/app-activities Yes info leaks are bad, but this isn't even an info leak if you start a completely new query it resets the original query variable e.g.: You search for query you'll get ?q set to query and ?oq set to query you search for query history it will set ?q to query history and keep ?oq set to query you search i got a rash on my butt it will reset both the ?q and ?oq URL parameters to the new query because it's unrelated. So you won't leak the fact that you searched for manliness enhancing spa treatments to your friends if you link them a query of a pole dancing cat. Your honor is safe my friend.
  - deleted 11y ago
    [deleted]
    - detaro 11y ago
      Nope, you can modify everything except the origin: https://developer.mozilla.org/en-US/docs/Web/API/History_API https://developer.mozilla.org/en-US/docs/Web/API/History_API
      - deleted 11y ago
        [deleted]
    - Rotten194 11y ago
      Yes they can, with `pushState`.
- xyzzy69 11y ago
  LMGTFY was that so hard?

dogma1138 11y ago

I don't think google search URL's were ever designed to be shared nor linked directly so I don't really see an issue here. The original query is stored in case you want to track back on the auto-suggest would you rather they to store those in cookies or non-volatile browser storage? And while it's true that if you link some one an entire Google URL search URL you might leak the original query, but given all the other dark magic that is in the URL which can include your client type, version, location and other things (e.g. inter-service referrals if you go there from another google service like Google Maps) i think the original query is the least of your worries. And if you want to link a query well just use https://www.google.co.uk/search?q=how https://www.google.co.uk/search?q=how to use google works just fine.

simoncion 11y ago
> I don't think google search URL's were ever designed to be shared nor linked directly... This is incredibly silly. URLs are how you get to a page. It's how The Web works! > The original query is stored in case you want to track back... That's what the History API is for. When you add an anchor-tag query, store the original state in the tab's history. > i think the original query is the least of your worries. Infoleaks are BAD. The least Google could do is use their URL rewriting powers to remove the original query when they add a query stored in the anchor-tag.
- dogma1138 11y ago
  > This is incredibly silly. URLs are how you get to a page. It's how The Web works! That's a very general and simplistic view of things, and we both know it's not true. While URL's were designed originally to only provide an address for a specific resource we all know they are also used for storage, user state management and many other things, again not ideal but in some cases unavoidable. Not to mention that URL's are not implicitly intended to be shared outside of the scope of your application you wouldn't link the 3 mile long URL that you get every time you login into your bank account would you? > That's what the History API is for. When you add an anchor-tag query, store the original state in the tab's history. Technically (best kind of not true) not true for the Google History API and even if it would be applicable for this it doesn't work in cases where you for example weren't signed in or explicitly blocking google tracking API's and services. Not to mention that making a API call every time you need to do something as basic as backtracking on your search is just pure insanity when it comes to resourcing. And if you are talking about the Chrome Page History API then why in god's name would i want a site to access it, not to mention it's not applicable in this case either. > Infoleaks are BAD. The least Google could do is use their URL rewriting powers to remove the original query when they add a query stored in the anchor-tag. Life is bad, if this was in a link which was automatically shared (although all those pin URL generators link 10 fold more data than Google) I would agree with you, otherwise not really this isn't a use case for the application.
  - simoncion 11y ago
    > ...we both know it's not true. I know no such thing. When I want to share a search result or anything else -that doesn't require authentication- with a friend, I copy the URL in the address bar and paste it to them. This is how The Web works. > ...if this was in a link which was automatically shared... I would agree with you [that this is a bad thing.] So, it would be acceptable to you if Google put your Google Account login and password in URI-encoded plain text in the URL of your search results? Why or why not? > Not to mention that making a API call every time you need to do something as basic as backtracking on your search... 1) Google already does exactly what I described when you make a search on *.google.com with a Javascript-enabled browser. It's what lets your back button work with their JS-based page updates. ;-) 2) A person driving his User Agent doesn't use the History API to go to a previous search result. He uses his back button or equivalent key combo.
    - dogma1138 11y ago
      >This is how The Web works. This is one of many ways the web works, URLs were designed way before there was an easy way to share them outside of the scope of the website it self. Looking at my history 50-60% of the URL's in it aren't humanly readable and are 10 miles long, many of them do not require authentication it would be nice if people would adhere to URL's are meant to be humanly readable and easy to share but you know... ...life. >Google already does exactly what I described when you make a search on *.google.com with a Javascript-enabled browser. It's what lets your back button work with their JS-based page updates. ;-) No it doesn't my back button works just fine and there isn't a single request made when i click it, just tried it know both with the network parses in chrome dev tools and fiddler. And again the history API isn't used for this not to mention it has been deprecated and turned into the App Activities API which has quite a different set of functions now, moments are still supported but it's pretty weird now. https://developers.google.com/+/history/ https://developers.google.com/+/history/ https://developers.google.com/+/features/app-activities https://developers.google.com/+/features/app-activities Yes info leaks are bad, but this isn't even an info leak if you start a completely new query it resets the original query variable e.g.: You search for query you'll get ?q set to query and ?oq set to query you search for query history it will set ?q to query history and keep ?oq set to query you search i got a rash on my butt it will reset both the ?q and ?oq URL parameters to the new query because it's unrelated. So you won't leak the fact that you searched for manliness enhancing spa treatments to your friends if you link them a query of a pole dancing cat. Your honor is safe my friend.
- deleted 11y ago
  [deleted]
  - detaro 11y ago
    Nope, you can modify everything except the origin: https://developer.mozilla.org/en-US/docs/Web/API/History_API https://developer.mozilla.org/en-US/docs/Web/API/History_API
    - deleted 11y ago
      [deleted]
  - Rotten194 11y ago
    Yes they can, with `pushState`.
xyzzy69 11y ago
LMGTFY was that so hard?