Answers.Body: <p>You can report infrastructure-related bugs on the "Infrastructure" project of JIRA (<a href="https://issues.civicrm.org/jira/browse/INFRA/" rel="nofollow">https://issues.civicrm.org/jira/browse/INFRA/</a>).</p>
  
  <p>I opened an issue for this: <a href="https://issues.civicrm.org/jira/browse/INFRA-175" rel="nofollow">https://issues.civicrm.org/jira/browse/INFRA-175</a></p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-04-14T12:11:19.657Z
Answers.LastActivityDate: 2016-04-14T12:11:19.657Z
Answers.UserDisplayName: bgm
Answers.Body: <p>If you experience this problem when trying to view the documentation it may be that your browser is either Chrome or Firefox and that you have previously visited the same page prior to 22 March 2016 (or for Firefox perhaps just visiting the main site <a href="https://civicrm.org" rel="nofollow">https://civicrm.org</a> could be enough).</p>
  
  <p>The gitbook link now redirects to <a href="http://docs.civicrm.org/user/en/4.6" rel="nofollow">http://docs.civicrm.org/user/en/4.6</a> (the read the docs version). The read the docs version previously used https and the switch to http can cause problems. I am not an expert on this but I know it has something to do with HSTS. I think that Chrome and Firefox will redirect to https even if you specifically enter http if the sub-domain previously used https. </p>
  
  <p>I was able to solve the problem with Chrome by deleting docs.civicrm.org from chrome://net-internals/#hsts (clearing caches or browser history did not work for me).</p>
  
  <p>I have not yet managed to solve the problem with Firefox. Again clearing caches or browser history did not work for me. </p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-03-25T12:47:01.173Z
Answers.Text: I thought it was working last night when I checked but that was from my phone -- this morning the browser in my computer is doing the same thing. (FF)
Answers.UserDisplayName: Laryn
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-03-25T12:55:55.737Z
Answers.Text: Someone with .htaccess permissions could try this... http://svictor.net/tools/joomla,-html-co/205-make-firefox-chrome-forget-hsts-for-your-site
Answers.UserDisplayName: Laryn
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-04-13T20:50:08.560Z
Answers.Text: `curl -s --head https://civicrm.org | grep Strict` shows no `includeSubDomains` so this setting has been preserved from previous docs.civicrm.org visits. If this HSTS setting is affecting visitors to docs.civicrm.org still, it is possible to clear HSTS on subdomains via the parent domain with `Strict-Transport-Security: max-age=0; includeSubDomains`. A better solution is to use SSL on docs.civicrm.org OR to not use an HSTS'd hostname on a non-SSL provider.
Answers.UserDisplayName: Chris Burgess
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-03-25T05:59:10.140Z
Answers.LastActivityDate: 2016-03-25T05:59:10.140Z
Answers.UserDisplayName: JoAnne
Body: <p>When I try to visit <a href="http://gitbook.civicrm.org" rel="nofollow noreferrer">CiviCRM's GitBook</a> I am forwarded to <a href="https://docs.civicrm.org/user/en/4.6" rel="nofollow noreferrer">https://docs.civicrm.org/user/en/4.6</a> with the following error:</p>
  
  <p><a href="https://i.sstatic.net/m6rDo.jpg" rel="nofollow noreferrer"><img src="https://i.sstatic.net/m6rDo.jpg" alt="Gitbook"></a></p>
  
  <p>Who should I report this to?</p>
  
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2016-03-25T00:45:03.873Z
Comments.Text: Was working for me an hour ago - and still is. As in I do not get redirected
Comments.UserDisplayName: petednz - fuzion
Tags: <documentation>
Title: Where to report Gitbook error (Problem loading page)
ThreadText: # Where to report Gitbook error (Problem loading page)
  
  (Asked by: username_0 on 2016-03-24)
  
  When I try to visit [CiviCRM's GitBook](http://gitbook.civicrm.org) I am forwarded to <https://docs.civicrm.org/user/en/4.6> with the following error:
  
  [![Gitbook](https://i.sstatic.net/m6rDo.jpg)](https://i.sstatic.net/m6rDo.jpg)
  
  Who should I report this to?
  
  **Tags:** documentation
  
  > **Comments:**
  > **username_1**: Was working for me an hour ago - and still is. As in I do not get redirected  
  
  ---
  
  ## 2 answers
  
  ### Answer by username_2 on 2016-04-14. Score: 2 | Accepted answer
  
  You can report infrastructure-related bugs on the "Infrastructure" project of JIRA (<https://issues.civicrm.org/jira/browse/INFRA/>).
  
  I opened an issue for this: <https://issues.civicrm.org/jira/browse/INFRA-175>
  
  
  ---
  
  ### Answer by username_3 on 2016-03-25. Score: 2
  
  If you experience this problem when trying to view the documentation it may be that your browser is either Chrome or Firefox and that you have previously visited the same page prior to 22 March 2016 (or for Firefox perhaps just visiting the main site <https://civicrm.org> could be enough).
  
  The gitbook link now redirects to <http://docs.civicrm.org/user/en/4.6> (the read the docs version). The read the docs version previously used https and the switch to http can cause problems. I am not an expert on this but I know it has something to do with HSTS. I think that Chrome and Firefox will redirect to https even if you specifically enter http if the sub-domain previously used https.
  
  I was able to solve the problem with Chrome by deleting docs.civicrm.org from chrome://net-internals/#hsts (clearing caches or browser history did not work for me).
  
  I have not yet managed to solve the problem with Firefox. Again clearing caches or browser history did not work for me.
  
  > **Comments:**
  > **username_0**: I thought it was working last night when I checked but that was from my phone -- this morning the browser in my computer is doing the same thing. (FF)  
  > **username_0**: Someone with .htaccess permissions could try this... http://svictor.net/tools/joomla,-html-co/205-make-firefox-chrome-forget-hsts-for-your-site  
  > **username_4**: `curl -s --head https://civicrm.org | grep Strict` shows no `includeSubDomains` so this setting has been preserved from previous docs.civicrm.org visits. If this HSTS setting is affecting visitors to docs.civicrm.org still, it is possible to clear HSTS on subdomains via the parent domain with `Strict-Transport-Security: max-age=0; includeSubDomains`. A better solution is to use SSL on docs.civicrm.org OR to not use an HSTS'd hostname on a non-SSL provider.  
  
  ---
  
  