Create a New Forum Admin Login Member Login Contribute to Voyager Search VoyForums Help Desk VoyForums Exchange VoyForums Directory/Categories VoyForums Homepage VoyForums News FAQ - Frequently Asked Questions

[ Show ]

Support VoyForums

[ Shrink ]

VoyForums Announcement: Programming and providing support for this service has been a labor of love since 1997. We are one of the few services online who values our users' privacy, and have never sold your information. We have even fought hard to defend your privacy in legal cases; however, we've done it with almost no financial support -- paying out of pocket to continue providing the service. Due to the issues imposed on us by advertisers, we also stopped hosting most ads on the forums many years ago. We hope you appreciate our efforts.

Show your support by donating any amount. (Note: We are still technically a for-profit company, so your contribution is not tax-deductible.) PayPal Acct: Feedback:

Donate to VoyForums (PayPal):

Saturday, February 22, 02:40:18pm

[ Login ] [ Contact Forum Admin ] [ Main index ] [ Post a new message ] [ Search | Check update time | Archives: 1, 2, 3, 4 ]

• No offense taken. But it is an accurate description of what's happening. Care to elaborate on what's happening if you think otherwise. (NT) -- eganonoa, Monday, February 17, 12:40:24am (NoHost/172.58.244.222)
  • Like you say, the SSL certificate is invalid so Chrome stops you. Chrome (Google) is notorious for security but it can be overridden in developer mode. Redirectig http to https is done server side and DNS has nothing to do with it at as the A records are the same and sends the request to the server with no idea if it is going to a secure or unsecure website. If it's a Linux box the .htaccess file redirects http to https and if it's a Windows box it's normally handled by the web config file... (NT) -- TT, Monday, February 17, 06:39:25am (74-95-251-150-Houston.hfc.comcastbusiness.net/74.95.251.150)
    • Not useful debate, but that's not accurate. Until recently voy http-only so some will have bookmarked and excepted tiff that way. Others accessing later will have a voy-enabled HSTS policy in place. That can be cleared (link inside) or a "new" browser works. But browser extensions like https everywhere or browser settings still enforce https policies non-server side & prevent access. Try it. Clear HSTS policy, access site, turn on strict https enforcement, stop accessing site -- eganonoa, Monday, February 17, 09:49:39am (pool-108-18-149-21.washdc.fios.verizon.net/108.18.149.21)
    • The proof of what I'm saying is in the fact that poster says it works in Edge but not Chrome. They're both at core the same browser these days since MS moved Edge to chrome. So why does it work in one, not the other? Settings and what the poster has used before. For me, I don't use stock "Chrome" on either desktop or mobile, but now have unfettered access to tiff on both using never-before-used completely stock Chrome browser. (NT) -- eganonoa, Monday, February 17, 10:04:17am (pool-108-18-149-21.washdc.fios.verizon.net/108.18.149.21)
    • So, as I say, while the underlying cause of this issue is the certificate expiry and HSTS enforcement by voy, it has ultimately nothing to do with why the poster above can access voy on Chrome but not reply, but can reply via Edge. The differences between the two browsers (neither of which are security-focused browsers) that the poster is experiencing are almost certainly due to settings, extensions and past use. Easiest thing for people to do is just use a stock browser they don't use for now. (NT) -- eganonoa, Monday, February 17, 10:08:43am (pool-108-18-149-21.washdc.fios.verizon.net/108.18.149.21)
    • And on the final point, dns servers, I'm specifically referring to instances where people may be using dns servers that use dns filtering and may have policies in place vs http sites. That, or other "network" wide settings (firewalls, port blocking) could prevent people accessing voy even if everything else on their browser would let them. Hence why I mentioned that. Anyway, I should stop discussing this now. Though not because I'm discussing something "I don't know about." Thanks (NT) -- eganonoa, Monday, February 17, 10:20:04am (pool-108-18-149-21.washdc.fios.verizon.net/108.18.149.21)