Skip to main content

If the site has previously indicated to Safari that it wishes to always be accessed over HTTPS through HSTS (HTTP Strict Transport Security), then Safari will always try to redirect to HTTPS.

You can clear the HSTS cache by deleting ~/Library/Cookies/HSTS.plist.

Note that Safari does also cache 301 redirects for a while and thus clearing the normal Safari cache may also be necessary: from the Develop menu (enable in Preferences → Advanced), choose Empty Caches.

#For 2020...

In current MacOS, you must

  1. Clear the cache in Safari and. (Developer menu.) Then immediately:
  2. Quit Safari, and any other apps that may use networking (quit all apps)
  3. Open /Users/ your user name /Library/Cookies which will look like:

enter image description here

  1. Throw HSTS.plist in the trash, then immediately restart the whole Mac.

In extreme cases, turn off all bandwidth to the Mac before steps 1-2-3-4.

In current MacOS, the HSTS list is immediately rebuilt if the file is thrown away, if any networking happens. Hence the Mac needs an immediate restart for trashing to work.

If the site has previously indicated to Safari that it wishes to always be accessed over HTTPS through HSTS (HTTP Strict Transport Security), then Safari will always try to redirect to HTTPS.

You can clear the HSTS cache by deleting ~/Library/Cookies/HSTS.plist.

Note that Safari does also cache 301 redirects for a while and thus clearing the normal Safari cache may also be necessary: from the Develop menu (enable in Preferences → Advanced), choose Empty Caches.

#For 2020...

In current MacOS, you must

  1. Clear the cache in Safari and immediately
  2. Quit Safari, and any other apps that may use networking (quit all apps)
  3. Open /Users/ your user name /Library/Cookies which will look like:

enter image description here

  1. Throw HSTS.plist in the trash, then immediately restart the whole Mac.

In extreme cases, turn off all bandwidth to the Mac before steps 1-2-3-4.

In current MacOS, the HSTS list is immediately rebuilt if the file is thrown away, if any networking happens. Hence the Mac needs an immediate restart for trashing to work.

If the site has previously indicated to Safari that it wishes to always be accessed over HTTPS through HSTS (HTTP Strict Transport Security), then Safari will always try to redirect to HTTPS.

You can clear the HSTS cache by deleting ~/Library/Cookies/HSTS.plist.

Note that Safari does also cache 301 redirects for a while and thus clearing the normal Safari cache may also be necessary: from the Develop menu (enable in Preferences → Advanced), choose Empty Caches.

#For 2020...

In current MacOS, you must

  1. Clear the cache in Safari. (Developer menu.) Then immediately:
  2. Quit Safari, and any other apps that may use networking (quit all apps)
  3. Open /Users/ your user name /Library/Cookies which will look like:

enter image description here

  1. Throw HSTS.plist in the trash, then immediately restart the whole Mac.

In extreme cases, turn off all bandwidth to the Mac before steps 1-2-3-4.

In current MacOS, the HSTS list is immediately rebuilt if the file is thrown away, if any networking happens. Hence the Mac needs an immediate restart for trashing to work.

Bounty Ended with 50 reputation awarded by Fattie
added latest info
Source Link
nohillside
  • 104.5k
  • 42
  • 222
  • 275

If the site has previously indicated to Safari that it wishes to always be accessed over HTTPS through HSTS (HTTP Strict Transport Security), then Safari will always try to redirect to HTTPS.

You can clear the HSTS cache by deleting ~/Library/Cookies/HSTS.plist.

Note that Safari does also cache 301 redirects for a while and thus clearing the normal Safari cache may also be necessary: from the Develop menu (enable in Preferences → Advanced), choose Empty Caches.

#For 2020...

In current MacOS, you must

  1. Clear the cache in Safari and immediately
  2. Quit safariSafari, and any other apps that may use networking (quit all apps)
  3. Open drive/Users/ your user name /Library/Cookies/Users/ your user name /Library/Cookies which will look like:

enter image description here

  1. Throw HSTS.plistHSTS.plist in the trash, butthen immediately restart the whole Mac.

In extreme cases, turn off all bandwidth to the Mac before steps 1-2-3-4.

In current MacOS, the HSTS list is immediately rebuilt if the file is thrown away, if any networking happens. Hence the Mac needs an immediate restart for trashing to work.

If the site has previously indicated to Safari that it wishes to always be accessed over HTTPS through HSTS (HTTP Strict Transport Security), then Safari will always try to redirect to HTTPS.

You can clear the HSTS cache by deleting ~/Library/Cookies/HSTS.plist.

Note that Safari does also cache 301 redirects for a while and thus clearing the normal Safari cache may also be necessary: from the Develop menu (enable in Preferences → Advanced), choose Empty Caches.

#For 2020...

In current MacOS, you must

  1. Clear the cache in Safari and immediately
  2. Quit safari, and any other apps that may use networking (quit all apps)
  3. Open drive/Users/ your user name /Library/Cookies which will look like:

enter image description here

  1. Throw HSTS.plist in the trash, but immediately restart the whole Mac.

In extreme cases, turn off all bandwidth to the Mac before steps 1-2-3-4.

In current MacOS, the HSTS list is immediately rebuilt if the file is thrown away, if any networking happens. Hence the Mac needs an immediate restart for trashing to work.

If the site has previously indicated to Safari that it wishes to always be accessed over HTTPS through HSTS (HTTP Strict Transport Security), then Safari will always try to redirect to HTTPS.

You can clear the HSTS cache by deleting ~/Library/Cookies/HSTS.plist.

Note that Safari does also cache 301 redirects for a while and thus clearing the normal Safari cache may also be necessary: from the Develop menu (enable in Preferences → Advanced), choose Empty Caches.

#For 2020...

In current MacOS, you must

  1. Clear the cache in Safari and immediately
  2. Quit Safari, and any other apps that may use networking (quit all apps)
  3. Open /Users/ your user name /Library/Cookies which will look like:

enter image description here

  1. Throw HSTS.plist in the trash, then immediately restart the whole Mac.

In extreme cases, turn off all bandwidth to the Mac before steps 1-2-3-4.

In current MacOS, the HSTS list is immediately rebuilt if the file is thrown away, if any networking happens. Hence the Mac needs an immediate restart for trashing to work.

If the site has previously indicated to Safari that it wishes to always be accessed over HTTPS through HSTS (HTTP Strict Transport Security), then Safari will always try to redirect to HTTPS.

You can clear the HSTS cache by deleting ~/Library/Cookies/HSTS.plist.

Note that Safari does also cache 301 redirects for a while and thus clearing the normal Safari cache may also be necessary: from the Develop menu (enable in Preferences → Advanced), choose Empty Caches.

#For 2020...

In current MacOS, you must

  1. Clear the cache in Safari and immediately
  2. Quit safari, and any other apps that may use networking (quit all apps)
  3. Open drive/Users/ your user name /Library/Cookies which will look like:

enter image description here

  1. Throw HSTS.plist in the trash, but immediately restart the whole Mac.

In extreme cases, turn off all bandwidth to the Mac before steps 1-2-3-4.

In current MacOS, the HSTS list is immediately rebuilt if the file is thrown away, if any networking happens. Hence the Mac needs an immediate restart for trashing to work.

If the site has previously indicated to Safari that it wishes to always be accessed over HTTPS through HSTS (HTTP Strict Transport Security), then Safari will always try to redirect to HTTPS.

You can clear the HSTS cache by deleting ~/Library/Cookies/HSTS.plist.

Note that Safari does also cache 301 redirects for a while and thus clearing the normal Safari cache may also be necessary: from the Develop menu (enable in Preferences → Advanced), choose Empty Caches.

If the site has previously indicated to Safari that it wishes to always be accessed over HTTPS through HSTS (HTTP Strict Transport Security), then Safari will always try to redirect to HTTPS.

You can clear the HSTS cache by deleting ~/Library/Cookies/HSTS.plist.

Note that Safari does also cache 301 redirects for a while and thus clearing the normal Safari cache may also be necessary: from the Develop menu (enable in Preferences → Advanced), choose Empty Caches.

#For 2020...

In current MacOS, you must

  1. Clear the cache in Safari and immediately
  2. Quit safari, and any other apps that may use networking (quit all apps)
  3. Open drive/Users/ your user name /Library/Cookies which will look like:

enter image description here

  1. Throw HSTS.plist in the trash, but immediately restart the whole Mac.

In extreme cases, turn off all bandwidth to the Mac before steps 1-2-3-4.

In current MacOS, the HSTS list is immediately rebuilt if the file is thrown away, if any networking happens. Hence the Mac needs an immediate restart for trashing to work.

added 79 characters in body
Source Link
grg
  • 205.6k
  • 45
  • 364
  • 495
Loading
Source Link
grg
  • 205.6k
  • 45
  • 364
  • 495
Loading