I'm not using the https link. I'm explaining why the problem isn't at the user end, it's at the site end. If the site responds on https, then it needs to correctly include https:// links for the active content. There's nothing I can do at this end, other than downgrade to a less secure version of the browsers I have that will change the behaviour.

I've already said before I disagree with the move towards https for everything but it's not something I can control.

https://support.mozilla.org/en-US/kb/mixed-content-blocking-firefox
https://developer.mozilla.org/en-US/docs/Web/Security/Mixed_content

@alfbranch can mitigate his issue by finding out why he's loading the https version and revert to the http version. However, if the website responds on https (which it does) then it must respond correctly otherwise it's broken (which it is).

 

Thanks for confirming that it's the https site that is broken, not the user end.

If you check closely, you'll see that if you already have the website open on the http connection, clicking an https link doesn't actually connect to the https site, your browser (probably for efficiency) uses the existing link and you get the http site.

Which is why I kept saying you have to type it in.

So the site responds on https, but it responds with broken content. It may be that for a short period the link from the home page was wrong and @alfbranch has an incorrect bookmark - remember that several people were getting this issue a week or so ago. It may be that @alfbranch uses something like https://www.eff.org/https-everywhere and that because the site does respond on https, it's always broken for him.

Why doesn't matter other than helping @alfbranch mitigate the specific issue. The underlying actual failure, the root cause, is that the site should either respond correctly on https or not at all.

 

This is the only website I use that has problems so as far as I am concerned it is this website that is at fault.

I am getting so pissed off I am going to stop using it.

 

Hi @alfbranch - does making sure you're going to http://www.amateurphotographer.co.uk/forums (i.e. http:// not https://) not resolve the issue? I don't know if you've got a bookmark to the https version, or a plug-in directing you to it, or something else, but in all of my testing, only the https:// version of the site fails. So if you can force your browser to use the http:// version, I think you should be okay.

 

Seems to have improved today I have only changed the theme a few days ago which did not seem to help at the time. neither showing http or https.

 

It hasn't improved for me.

I'm getting increasingly reluctant to visit.

MickLL

 

You need to click in to the address bar to see if you're using http:// or https://

 

but many browsers don't show that - they start at www but if it is https they should provide a padlock sign and if it isn't they may warn the site is insecure.

The only way I could reproduce this was by manually typing the https address. Following the https link seemed to parse first to AP site (https) and then to /forums (http) and not go to https::// ....../forums. So I really don't understand what is happening for Alf and for Mick.

I also tried it for both forum style pages and that choice made no difference.

 

I don't know why they're reaching the https site either (I'm not sure Mick has the same issue). But I do know that if the web server responds on https:// then it has to respond properly which it's not doing, and the stuff alf sees is exactly the same as I see if I go to the https:// site.

 

I am still having an issue and am visiting less as a result. Here's an example:

I get to the website through a 'favourite' and always get to the screen that I'm used to . The address bar in that case is very similar to the one I'll show below. I got to this thread by clicking on the 'latest posts' bit on the right. The address bar is as below:



Then to go elsewhere I go to the top of the screen click on the 'ap community' link (at least I think that's it because I'm logged in and using the default view I can't check) and get the problem page that I've posted before. The address bar is then :



I still have had no response at all from me reporting the issue. If it's all my fault then I would very much like to know what to do about it.

MickLL

 

That second entry shows you're connecting to the https site, I don't know why, but it won't work when you do. You need to remove the https:// and replace it with http://

 

That's OK but I don't want to be doing that every time I change pages - or have I got it wrong?

MickLL

 

I get: http://www.amateurphotographer.co.uk/forums/forums/ap-magazine-feedback-suggestions.86/

which is what you should get.

The code to link from the AP page to forums is <li id="menu-item-33001" class="menu-item menu-item-type-custom menu-item-object-custom menu-item-has-children no-icon menu-item-33001"><a href="http://www.amateurphotographer.co.uk/forums/"><span>Forum</span><span class="mobile-drop-down icon-down"></span></a>


Once you are inside the forum all links appear to be local to http://www.amateurphotographer.co.uk/forums

There appears to be no way to navigate to your link.

 

I can't find any page with an ap community link.

 

It's not a link - third header on the forums page

Forum notices
AP Magazine
AP Community
.
.
.

 

Sorry - this is what I meant - click on "AP magazine feedback and suggestions"



MickLL

 

Have you done this ?

HTTPS Everywhere is a Firefox extension to protect your communications by enabling ... The HTTPSEverywhere extension fixes these problems by rewriting all requests to these sites to HTTPS. ...

I googled ... "is there an option to make Firefox force all connections to https" and found an advert for HTTPS Everywhere

 

A further useful google search is how to stop redirect from http:// to https://

I'm not spending any more time on this - it is a browser issue.

 

No it's not. It's a site issue. If the site responds on https it must respond properly.

 

Meanwhile, back in the real world, it's a browser issue to all intents and purposes, because it doesn't look like there will be a site resolution for a while, plus there must be some broser-related problem that Mick has.