google search result links are links to google redirects, not to the results

 For years, google search results have consisted of links not to the result pages, but to google-based redirects.

This seems like a strange choice by google.  They break all kinds of things, including the user getting the URL of a linked page from their browser.  I want to do this all the time.  One workaround is to follow the link, and then copy it from the address bar instead.

If they put the correct URL for the link target, and added a bit of javascript to notify them for tracking when followed, this would work in over 99% of cases.  What extra are they gaining, that justifies breaking the copy-link-location feature, that is a basic way of how the web works (or could work)?

Instead, they seem to have added javascript to incorrectly and deceptively display the right URL in the user's status bar, despite the real link pointing at google's own servers.

In this example, the status bar is spoofed to say something under www.heathrowmedical.com, but the real target of the link is  https://www.google.com/url?sa=t&rct=j&q=&esrc=s&source=web&cd=&cad=rja&uact=8&ved=2ahUKEwj7v5yooMX0AhXn_7sIHVJ4DeQQFnoECAYQAQ&url=https%3A%2F%2Fwww.heathrowmedical.com%2Fcovid-19-testing%2F&usg=AOvVaw15oqm7QsP4u3L2j8ZGDc_L :


but in the following one, a different entry on the same results page, the status bar is left to display the google-hosted track-and-redirect:



 
 
Is that because their javascript to spoof the status bar doesn't work in all cases, or they are choosing not to spoof it in all cases?

Comments

Post a Comment

Popular posts from this blog

the persistent idiocy of "privileged ports" on Unix

TCP and UDP have ports.  These are 16 bit; there are 65535 or so per IP address. These protocols don't care to differentiate between the ports.  Elsewhere, IANA presumes to operate a process to allocate "well-known" ports in the range 1-1023, "registered ports" in the range 1024-49151, and to reserve the remainder, 49152–65535, for "ephemeral" ports.  The caller end has to have a port, which is how replies get back within the virtual connection, and these are conventionally picked from the ephemeral range by the OS's networking stack. The whole idea of ports is ridiculous, because it allows ISPs to arse around presuming to decide which services they will "not allow".  Anything that allows IPSs to do anything other than shift opaque packets will allow ISPs to meddle and break things, and due to the Law of Meddling, if they can, they will.  I am currently working around an issue with Claro, a pretend ISP, blocking port 5060, allocated to SI...
Read more

easyjet: repeated entry of information they already have

Image
As I observed earlier today, airline web sites are obsessed with making people re-enter information, apparently arbitrarily. The following seems to be required for Easyjet, for an "existing" customer relationship, every time: country of residence selected from big list, involving skidding around on the screen that makes the victim feel sick should be remembered. If it has to be changed, should be type-and-choose victim is taunted with the text "tell us about you", when they thought they had logged in form with the following on one page: business / leisure title, first name, last name, age there is a button to "copy from contact details", but this doesn't do the "age" field.  Since they have my date of birth, they are of course able to calculate my age.  As well, the only values for this field are "18+", "17", or "16".  Is it a deliberate decision, to not fill this field based on the customer data, and to make the...
Read more

Guernsey Waste in incorrect bag-rejection horror May 6th, 2024

Image
The rubbish collection folk at my new place seem pickier than at other places on Guernsey. Last week, they removed some card packaging that I'd included in the card and paper (plastic) clear bag, and left it on the lane.  This week, they have attached a rejection label entitled "Polite Notice".  Just like modern software-engineered error messages (see attached tag "extremely_general_error_handling"), this does not give a specific reason why the bag was rejected, but instead lists miscellaneous possible "reasons", leaving the victim guessing, or perhaps trying to follow a process of elimination. In this case, some possible reasons, which the label does not claim to be exhaustive ("was most likely because ..."), and of which none apply, are: (i) "did not have the required payment sticker" -- no, I applied to 90 litre sticker; or  (ii) (a) "too heavy" -- no, I estimate it was 3kg, and I easily supported the bag's weight o...
Read more