I decided to try 76 RC, but was surprised to find that my startup page http://localhost/index.php does not work. Instead, it is changed to http://www.localhost.com/index.php, and then it is reported that the URL does not exist.

My original reason for trying the 76 RC was due to so many websites reporting that this version of Firefox browser is out of date, and that I should upgrade to a later version of Firefox. Also, Adobe Flash seems to fail in K-Meleon, however I have had an occasional video display right after an Adobe update, but soon after, videos no longer show.

Quote
Gary
I decided to try 76 RC, but was surprised to find that my startup page http://localhost/index.php does not work. Instead, it is changed to http://www.localhost.com/index.php, and then it is reported that the URL does not exist.

My KM 76 RC2 does not change the name, but does not find a file. Of course I do not have a localhost/index.php to be found. Physically, where is your file?

Gary, if the file is on your local hard drive, you shouldn't use "localhost", because K-Meleon doesn't recognize it and tries to find it on the web. Even if you don't start with http:// it will add it automatically. Try using "file://" instead, plus the path to your file.

For example: file://C:/Users/someone/someplace/index.php

I remember having to specify "localhost" for local files when I used Opera a long time ago, but it seemed odd.

PS: And I don't understand why KM (and Firefox) add a third slash before the path, e.g. file:///C:/, even though they let me enter that with just two slashes. I haven't seen that in non-Mozilla browsers.

---
Gerry



Edited 3 time(s). Last edit at 01/26/2017 12:19AM by foliator.

>My KM 76 RC2 does not change the name, but does not find a file
By changes, I mean it changes to checking for a file served at http://www.localhost.com instead. Of course it doesn't change the name of my file, but it reports the URL as if it were one on the web when it should be using the local server.

>"Physically, where is your file?"
It is located in a directory at or below where the Document Root set up in the Apache config file. It does not matter exactly where as long as it is at or below the location specified in the Document Root setting. Most common LAMP setups will default to having Document Root at a directory below the root of the LAMP install location. People who test different browser and servers as I do, know that it is better to specify a location other than below the LAMP install. I typically use a totally different drive letter and directory. All LAMP setups I test will have the Document Root set to the same location. That way, I can stop one server, and start another server, and the URL in the browser will not need to be changed.

Valid URLs of the same file:
http://localhost/directoryA/subdirectoryB/subdirC/file.php
localhost/directoryA/subdirectoryB/subdirC/file.php
127.0.0.1/directoryA/subdirectoryB/subdirC/file.php
127.0.0.1:80/directoryA/subdirectoryB/subdirC/file.php

Refer to my post before for more specifics.

>if the file is on your local hard drive, you shouldn't use "localhost", because K-Meleon doesn't recognize it and tries to find it on the web.
That is the bug I am pointing out. You can't say "because K-Meleon doesn't recognize it" as reason why this is a mute point. That is the problem; it should recognize it. The browser is not supposed to ignore the localhost URL and instead look for it on the web. It is supposed to use the localhost part to understand that the server is running locally, which is the same as K-Meleon has done historically as far back as I can remember (all the way up to and including 75.1), and the same as other browsers have done, still do, and will into the future. If the url is http://localhost, or if it is merely localhost, localhost/name.html, localhost/name.php, or even if it is 127.0.0.1, the browser is supposed to check for a running server locally, and use it. By default, the IP address will be 127.0.0.1, and using port 80.

I have K-Meleon 75.1 installed, and it recognizes the URL the same as it always has, and the same as other browsers do.

As a developer that has written more browser code than most, I do know how this is supposed to work.

If file:// was the way to do this, you wouldn't need to run a server. Since browsers interpret simple HTML, it can handle the protocol file:// as a way to start the simple processing and display. While you can use file: as the protocol for simple html files, it does not work for files that need to be pre-processed (e.g., php, asp, etc). That is why browsers need to use the localhost as the clue to allow the local server to serve the document.

Sorry, but that is just how things are supposed to work, and why they still do, ... except for version 76 RC.

What you should do is install a LAMP and get experienced with how things work if you are going to post responses to these types of issues.

@foliator, that has no sense.

Localhost is 127.0.0.1 in all Windows and Linux. I run my own web server and it would be a bad day if I couldn't use localhost as url hostname.

@Gary, I don't use 76 version, so I can't help much, but check Edit menu > Preferences > Browsing section > Finding websites. There, uncheck the domain autocompletion and restart K-meleon.

If that doesn't change anything, it might be a new Bug or maybe system specific if 75 works.



Edited 1 time(s). Last edit at 01/26/2017 02:51PM by JohnHell.

@Gary: OK, sorry about my ignorance about tech stuff. I'm neither a web designer nor a developer, don't run a server, and I also overlooked the fact that your file was a .php.

At any rate, I'm currently using KM 75 (not 75.1), and localhost definitely does not work here for my local HTML files, either with or without http://. As I mentioned above, it did work in an old version of Opera, and in fact, I couldn't bring up my local files in Opera without it.

---
Gerry

For localhost urls you need a server.

So http://localhost/whatever.html doesn't load a local file, but a file served by a server.

What Opera does is rewrite the URL.

When Opera displays file://localhost/c:/x.html, what it is actually doing is open file:///c:/x.html.

Do the test and you will see, foliator



Edited 2 time(s). Last edit at 01/26/2017 03:55PM by JohnHell.

Quote
JohnHell
What Opera does is rewrite the URL.

When Opera displays file://localhost/c:/x.html, what it is actually doing is open file:///c:/x.html.

Do the test and you will see, foliator

I no longer have Opera to test it with, but thanks for the explanation. Now I see that KM will accept localhost if used between the second and third slash, like in your example, but then removes it from the URL when the file opens.

What's interesting is that IE (up to IE9 at least) allowed me to enter just the path and file name without any prefix at all, and even use backslashes. I just tried it in K-Meleon, which converted it to a proper URL with file:/// and forward slashes.

---
Gerry

Under linux, with Opera

file://localhost/home/alain/so.html

is equivalent to :

file:///home/alain/so.html

Under linux with K-Meleon

file://localhost/Z:/home/alain/so.html

is equivalent to

file:///Z:/home/alain/so.html

So, localhost is really not necessary in all cases :cool:


A+

---

Mozilla/5.0 (x11; U; Linux x86_64; fr-FR; rv:38.0) Gecko/20100101 Ubuntu/12.04 K-Meleon/76.0

---

Web: http://jujuland.pagesperso-orange.fr/
Mail : alain [dot] aupeix [at] wanadoo [dot] fr

---

Ubuntu 12.04 - Gramps 3.4.9 - Harbour 3.2.0 - Hwgui 2.20-3 - K-Meleon 76.0 rc

---

Quote
JujuLand

So, localhost is really not necessary in all cases :cool:


A+

I'm afraid there is a misunderstanding.
Imagine you are running a local server e.g 127.0.0.1:8000
You want to retrieve files located on that server.
First you'll have to connect to that server in order to get the files.
Basically it's the same procedure as if you visit a site in the World Wide Web.