K-Meleon displays unauthenticated (http://...) versions of web pages that should be authenticated with SSL/HTTPS (https://...).

I have set up a subdirectory on my web site with an .htaccess file to redirect all HTTP requests for the subdirectory and any files or directories in its subtree to the HTTPS version of the requested URI. That is, the server will respond as though the URI "https://papa.myjp.net/secure/index.html"; was requested if any of the following addresses are entered in the browser prefixed with either "https://"; or "http://";, or no prefix:

papa.myjp.net/secure
papa.myjp.net/secure/
papa.myjp.net/secure/index.html

All browsers that I've tested other than K-Meleon (Brave, Chrome, lynx, OrFox, Vivaldi, and a few others) treat the above addresses as expected.

K-Meleon displays the expected HTTPS-redirected version of the page for the first variation above ("...secure" with no terminating "/"). However, for the other two variations (terminated with "/" or with explicit index file name) K-Meleon displays the page with an "http://..."; URI shown in the address bar and an unlocked security icon on the lower right-hand corner of the browser frame.

Can anyone recreate this problem? Is it a bug?

As you may have seen in the logs, I didn't had any problems.

What version are you using? (Please, give exact details so others can test it)

Did you setup anything, or are you running K-meleon out of the box?



Edited 1 time(s). Last edit at 11/13/2018 12:30AM by JohnHell.

I'm running K-Meleon 75.1 out of the box on Windows 7 Professional.



Edited 1 time(s). Last edit at 11/13/2018 01:00AM by papa.

Quote
papa
I'm running K-Meleon 75.1 out of the box on Windows 7 Professional.

I'm not going to build an environment just to test that (I'm using 75.0 in other system), but I used it and I hadn't problems with those redirects in the past with K-meleon 75.1.

Anyway, unless you need to test it against that version, you can try the latest, that even at front page appears as test build, might be considered as a live development/upgrade version:
http://kmeleonbrowser.org/forum/read.php?19,143253

75.1 is not the latest version anymore so those "bugs" won't be fixed.

76 is the latest, based in Gecko engine, despite the RC description.

And 76G or 77 is the latest based in Goanna engine.

In the other hand, is strange what you tell. Shouldn't happen out of the box.



Edited 2 time(s). Last edit at 11/14/2018 01:08AM by JohnHell.

Quote
papa
papa.myjp.net/secure
papa.myjp.net/secure/
papa.myjp.net/secure/index.html

All browsers that I've tested other than K-Meleon (Brave, Chrome, lynx, OrFox, Vivaldi, and a few others) treat the above addresses as expected.

So does K-Meleon as well.
Tested with K-Meleon 76 - Goanna.

Site papa.sdf.org/secure

Welcome to my web site.

Tested on KM76G, build 20180825_02.

Are you accessing your site from within your server? That is, looking directly at your files on disk? This is a common test failure: you must access your site from a remote location, for example a university computer, or a friend's box.

____________________
Understanding the scope of the problem is the first step on the path to true panic. [Florence Ambrose, "Freefall" 01372 January 22, 2007 http://freefall.purrsia.com/ff1400/fv01372.htm]

It could be ISP related, i.e. they have mcafee installed down the pipes.