09-08-2021, 11:10 AM
(This post was last modified: 09-10-2021, 07:47 PM by CardBoardBox.
Edit Reason: added PS
)
I spent a lot of time previously trying to solve it. The problem surfaced lots during a period, then not at all during other times.
Note I'm on the continually updated FF version, and using unpatched (2 years) Windows 7, which generates lots of internal errors about 'cross domain' incompatibilities, I've never been totally prohibited.
Usually I see zero ads, and usually (99% of the time I am using just HTTP) I have found when reaching the dead end, I back-page, and as soon as the expected URL shows up, I hit escape (or stop) and insert an HTTPS colan slash slash in the front of the url, push the return-key and end up being able to post a reply, which I just had to do today both times.
Google analysis and google ads seemed a part of the problem. The fact that our "friend" is not in the US, the ads he sees, or at least the program is checking, just might be a cause of the problem. You all know targetted advertising, Canada sees ads for lobsters and we see ads for ED and electric drink mixers.
I thought it had to do with page resizing at one time.
Kylake is a good guy for trying.
-------
POST SCRIPT, after TAH's post (below) for I don't want to always be the last poster in a thread; DToT has tried the HTTPS, and there were changes to some places in the code/related programs to retain the HTTPS once it has begun, but he still can not get his reply to function.
Many a day using plain http startup works fine, then it won't for several days. Logic eludes me, same as why I see ads and don't see ads here.
Note I'm on the continually updated FF version, and using unpatched (2 years) Windows 7, which generates lots of internal errors about 'cross domain' incompatibilities, I've never been totally prohibited.
Usually I see zero ads, and usually (99% of the time I am using just HTTP) I have found when reaching the dead end, I back-page, and as soon as the expected URL shows up, I hit escape (or stop) and insert an HTTPS colan slash slash in the front of the url, push the return-key and end up being able to post a reply, which I just had to do today both times.
Google analysis and google ads seemed a part of the problem. The fact that our "friend" is not in the US, the ads he sees, or at least the program is checking, just might be a cause of the problem. You all know targetted advertising, Canada sees ads for lobsters and we see ads for ED and electric drink mixers.
I thought it had to do with page resizing at one time.
Kylake is a good guy for trying.
-------
POST SCRIPT, after TAH's post (below) for I don't want to always be the last poster in a thread; DToT has tried the HTTPS, and there were changes to some places in the code/related programs to retain the HTTPS once it has begun, but he still can not get his reply to function.
Many a day using plain http startup works fine, then it won't for several days. Logic eludes me, same as why I see ads and don't see ads here.
