Этот сайт имеет ограниченную функциональность, пока мы проводим техническое обслуживание для улучшения его работы. Если какая-либо статья не решила вашу проблему и вы хотите задать вопрос, наше сообщество поддержки ждёт вас: @FirefoxSupport в Твиттере и /r/firefox на Reddit.

Avatar for Username

Поиск в Поддержке

Избегайте мошенников, выдающих себя за службу поддержки. Мы никогда не попросим вас позвонить, отправить текстовое сообщение или поделиться личной информацией. Сообщайте о подозрительной активности, используя функцию «Пожаловаться».

Подробнее

Эта тема была архивирована. Если вам нужна помощь, задайте новый вопрос.

using https://domain.com prevents any use of http://anything.domain.com

amirtal2000
amirtal2000
more options

using https://domain.com prevents any use of http://page1.domain.com or http://page2.domain.com

explanation: see previous question ""I understand the risks" option missing - page is read from cache" (no unique id available for every question ?!?!)

when working with https sites, adding an exception to https://domain.com prevents ANY links for http://anything.domain.com to open, either with "Unable to connect" or "The page isn't redirecting properly" or with a security warning for the site certificate (in case of self signed and/or expired).

in all cases, this PREVENTS the sub-domains to open at all, until exception is manually removed from firefox (only possible with SQlite DB editor extension !!!!!!) and issue is re-created whenever accessing https://domain.com again !

this DOES NOT happen on chrome, opera, and even IE (!)

using https://domain.com prevents any use of http://page1.domain.com or http://page2.domain.com explanation: see previous question ""I understand the risks" option missing - page is read from cache" (no unique id available for every question ?!?!) when working with https sites, adding an exception to https://domain.com prevents ANY links for http://anything.domain.com to open, either with "Unable to connect" or "The page isn't redirecting properly" or with a security warning for the site certificate (in case of self signed and/or expired). in all cases, this PREVENTS the sub-domains to open at all, until exception is manually removed from firefox (only possible with SQlite DB editor extension !!!!!!) and issue is re-created whenever accessing https://domain.com again ! this DOES NOT happen on chrome, opera, and even IE (!)

Выбранное решение

Link to your earlier thread: "I understand the risks" option missing - page is read from cache - problem with Strict Transport Security header on base domain applying to all subdomains.

I think this actually is the same problem.

Прочитайте этот ответ в контексте 👍 1

Все ответы (2)

guigs
guigs
more options

If the page is read from the cache and you select a permission for that page, when you click I understand the risks it can remember that option or not. There is a work around for this. If you add the https://domain.com to the exceptions list

check out about:permissions If you add the webpage to the list and manage cookies, this may be a good place to avoid this. Once you set the permissions for the https site, can you load the page by bypassing the cache and let us know if this still happens? Reload the webpage while bypassing the cache using one of the following steps:

  • Hold down the Shift key and click the Reload button with a left click.

OR

  • Press Ctrl + F5 or Ctrl + Shift + R (Windows and Linux)
  • Press Command + Shift + R (Mac)

Let us know if this solves the issues you are having.

jscher2000 - Support Volunteer
jscher2000 - Support Volunteer
  • Top 25 Contributor
more options

Выбранное решение

Link to your earlier thread: "I understand the risks" option missing - page is read from cache - problem with Strict Transport Security header on base domain applying to all subdomains.

I think this actually is the same problem.