Why does Chrome always redirect me to https://www.google.com

google-chrome ssl https

23,709

I'd say it's because their web servers send the HSTS header (http://en.wikipedia.org/wiki/HTTP_Strict_Transport_Security).

23,709

Tode

Hi there, my name is Torsten and I work with Workflow / Groupware Software since 1995. I really love HCL Notes / Domino (formerly known as IBM Notes Domino, formerly known as Lotus Notes / Domino) and work with the software since Version 4.5. Recently I startet using something very similar called Intrexx by United Planet and I love that product for the same reasons I love Notes: the simplicity of rapid development in Lowcode / Nocode environments paired with the possibility to write highly advanced, object oriented business logic code on the same platform. I prefer so see myself not as a software developer but problem solving specialist. Knowing LotusScript, Lotus @Formula, Java, JavaScript, Python, Groovy and Apache Velocity helps me achieve that goal. Feel free to contact me. I might be able to solve your problems as well. Best regards Torsten

Updated on September 18, 2022

Comments

Tode over 1 year

Whenever I enter "http://www.google.de" (or any other google domain) in the addressbar, it is automatically replaced by "https://www.google.de".

This happens regardless of beeing logged in with my google account or not. There are some hints on the web, that this behaviour can be disabled, but unfortunately google changed something, and these options are not available anymore (see here)

In the network I am at the moment all SSL- traffic is directed over a "man-in-the-middle"- proxy, so that chrome will not let me open the https:// - links (certificate error).

that's why I want to disable this feature. Anyone who can help me with that?

Before I forget: Chrome version is 27.0.1453.110

EDIT: This has NOTHING to do with the omnibox- search... Chrome just rewrites any google- url I enter...
- f1assistance almost 11 years
  
  Network admins and their silly attempt to implement security protecting domain resources from promiscuous surfers sure can be frustrating for those users who don't want to play by the rules...
- Tode almost 11 years
  
  you are so true... Problem is: In this constellation I can not use google to search in chrome at all... I cannot use http:// as chrome redirects and i cannot use https:// due to the proxy... right now I search google with IE...
- Barmar almost 11 years
  
  Does this only happen with Chrome?
- Tode almost 11 years
  
  Yes, IE does not do this
- MattDMo almost 11 years
  
  have you tried Firefox? I've found it has many more config options than Chrome, especially if you use about:config as a URI.
- Tode almost 11 years
  
  That was not my question... Yes I could use another browser, it works with them.. My question was related to using Chrome...
- trlkly almost 10 years
  
  I would say that, if there's a man-in-the-middle issue for HTTPS, it's almost certainly there for HTTP as well. Why would someone only want to monitor HTTPS and not HTTP? It's just that HTTP has no way to inform you. Thus you'd be no worse off forcing Chrome to temporarily allow the bad certificate. Just avoid doing anything that actually needs to be kept secure.
Tode almost 11 years

This sound exactly like the behavior I see... I will check, if I can let chrome ignore hsts- requests...
PrecariousJimi almost 11 years

You're somewhat right. Note that Chrome has list of HSTS-enabled domains pre-loaded by default. No need to send separate header for them. Source: src.chromium.org/viewvc/chrome/trunk/src/net/http/…
Tode almost 11 years

The additional comment of Ilya Zakreuski proved: Yes, this is the reason for redirection, and there seems no way, to disable it. SO this is the answer to my question.