Safari is forcing HTTPS on everything when I don't want it to

Question

Level 1

11 points

Safari is forcing HTTPS on everything when I don't want it to

On my localhost development environment, when I manually browse to

http://localhost

it automatically redirects me to

https

every time.

And I get this error:

When I do the same in chrome, it successfully goes to

http

.

Is there anyway I can mitigate this or to get https to work on my local dev servers? Any help would be greatly appreciated because until I fix it I can't use safari.

MacBook Pro (15-inch, Late 2016), macOS High Sierra (10.13.1), Safari Version 11.0.1 (13604.3.5)

Posted on Nov 9, 2017 10:53 AM

Reply

Answer 1

Best reply

bgold0 Author

Level 1

11 points

Nov 9, 2017 12:03 PM in response to Kappy

I hope you don't think I'm that dumb. I've tried that.

Proof if you don't believe me: https://imgur.com/b6E2fZs

Reply

Answer 2

bgold0 Author

Level 1

11 points

Nov 9, 2017 7:58 PM in response to PN2

I've checked my hosts, deleted the HSTS file in ~/Library/Cookies/, and cleared my cache. Still the same thing 😟

Reply

Answer 3

bgold0 Author

Level 1

11 points

Nov 9, 2017 1:31 PM in response to Kappy

What are you talking about? I said "On my localhost development environment, when I manually browse to

http://localhost

it automatically redirects me to

https

every time."

It's a local development server. I'm a web developer.

Reply

Answer 4

Kappy

Level 10

361,741 points

Nov 9, 2017 2:36 PM in response to bgold0

I am not working on a server. On my machine both https:// and http:// w/localhost results in the same error page because localhost here is 127.0.0.0. Using http:// does not result in Safari changing it to https://. I'm afraid I don't know what your problem is.

Reply

Answer 5

PN2

Level 4

1,052 points

Nov 9, 2017 3:22 PM in response to bgold0

macos - Safari Redirecting http to (non-existent) https - Ask Different but the suggestion to modify hosts seems to be adding what is part of a default hosts file anyway. I'd start with the HSTS file.

Although users elsewhere report near-identical problems with Chrome : but it's a start.

Reply

Answer 6

PN2

Level 4

1,052 points

Nov 9, 2017 8:27 PM in response to bgold0

I've seen some Safari threads where users said the file needed to be trashed, then the computer restarted immediately for it to work... but you can read the psi in Terminal or a text editor to see if there's an entry relating to localhost or 127.0.01 etc

If not : does a new or Guest user have the same problem, ?.

Reply

Answer 7

Kappy

Level 10

361,741 points

Nov 9, 2017 11:06 AM in response to bgold0

Just remove the 's' and try again.

Reply

Answer 8

Kappy

Level 10

361,741 points

Nov 9, 2017 12:05 PM in response to bgold0

How can you expect me to know what you've done when you don't bother to tell me? Why are trying to access localhost? That is typically a dead-end at IP 127.0.0.0.

Reply