Jump to content

ClusterHead

Members
  • Posts

    171
  • Joined

  • Last visited

Posts posted by ClusterHead

  1. Copying this from the support thread:

    Something that you may want to pass along to the board developers that I just uncovered in my testing:

    When navigating to a topic in the site using https://..., the pagination fails to load as we get client-side errors when attempting to jump between http:// and https://.  However, http://... has worked every time that I have tested pagination.  I suspect that this works because http:// doesn't care if resources are served up via http:// or https://, it just works.  This has been the case with every single one of my tests on several random threads across multiple boards on the site.

    NOTE:  it is not recommended to navigate to a site over http as it is not a connection secured with an SSL certificate.

    As an example using the support thread:

    In short, if you see a padlock to the left of the address bar then the site is over https and will not allow page changes.  If you see a "Not Secure" message instead of a padlock, then you are on http and paging should work without issue.  

  2. On 5/17/2022 at 2:29 PM, HoosierFaithful said:

    We are getting closer - as a temporary workaround, please navigate to the bottom of the forum and click to change your theme to "test default" and see if that fixes errors.

    Something that you may want to pass along to the board developers that I just uncovered in my testing:

    When navigating to a topic in the site using https://..., the pagination fails to load as we get client-side errors when attempting to jump between http:// and https://.  However, http://... has worked every time that I have tested pagination.  I suspect that this works because http:// doesn't care if resources are served up via http:// or https://, it just works.  This has been the case with every single one of my tests on several random threads across multiple boards on the site.

    NOTE:  it is not recommended to navigate to a site over http as it is not a connection secured with an SSL certificate.

    As an example using this thread:

    In short, if you see a padlock to the left of the address bar then the site is over https and will not allow page changes.  If you see a "Not Secure" message instead of a padlock, then you are on http and paging should work without issue.  

    • Like 1
    • Thanks 1
  3. Did a little more digging (at least as best I can from my browser's console) and it appears those may be failing to load due to them being served over HTTP instead of HTTPS.   

    There is also a JS promise that looks to be failing when trying to pull cached assets which would explain why a cache refresh fixes the issue in the short term.  Sorry for getting a bit technical, but I can share my findings with mods if this isn't the place to continue the conversation.

    • Like 1
    • Thanks 4
  4. 1 hour ago, Inequality said:

    My opinion is its possibly been a redirect issue. Redirects reduce server load. Too many could be the issue. Basically, if it loads, your getting an non-functioning image. Which is what I have been getting. I’ve not been able to log on most of the day.

    I ran a network trace in Chrome's dev tools...didn't see any 300 HTTP codes indicating a redirect to the client.  However, I am seeing that there are three resource files that are currently failing to load which may be a good starting point to look over:

    image.png.e0b79c2e5c66e93b2a1dfea9d4f42689.png

    • Like 1
×
×
  • Create New...