Welcome to WebmasterWorld Guest from 126.96.36.199
Forum Moderators: phranque
We've recently become aware that at least one organization (A VA hospital where a customer of ours works) doesn't allow access to our website. We're not sure why. I'm wondering if it's because it's not https,
Are there browsers, or browser settings (for home / mobile users) or firewall appliances (for institutional / corporate users) that are limiting / blocking access to websites that they can't connect to using https secure protocols? Even if there is nothing that the user can do on the site that would require security of any kind?
joined:Sept 30, 2018
I'd be more concerned about your 2001 design.Paradoxically, a very very old site* may in fact be more responsive than a newer one, as itís less likely to contain directives that assume the user's viewport is some-vast-number-of-pixels wide.
I don't think IIS4 can do https. I really don't want to have to mess with it. And - don't I have to pay someone like verisign for an SSL certificate?
not mobile friendlyIt should be pointed out that rendering is not the only aspect of mobile-friendliness, though it's certainly the first and most obvious one. Google also notices things like clickable areas being too close together (because a fingertip is bigger than a mouse pointer). Ask your cell-phone-users if they find any trouble spots navigating the site.
the site renders just fine