Bugs :  K-Meleon Web Browser Forum
You can talk about issues with k-meleon here.  
http error 404 with open in bg
Posted by: Andres
Date: November 25, 2001 04:27AM

When I am using K-Meleon through AnalogX Proxy (http port 6588) on Windows 98SE, I am quite frequently having a strange sort of bug here. It happens when I click "Open in Background" on a link. On a fairly large amount of cases, K-Meleon returns me an error message "HTTP Error 404 - 404 Not Found - The Web server cannot find the file or script you asked for. Please check the URL to ensure that the path is correct." However, the same links work much more frequently with Open in New Window and always work with Internet Explorer. And I do know that those links must actually work.

The same error message comes with Mozilla 0.9.5 when I use the "Open in New Tab" option. In K-Meleon (I am using either the Default or Netscape 6.1/Mozilla Browser ID string), this tends to happen more frequently when my disk cache is full or when I have many Windows open, although this is not a rule. I would not have posted it here unless Internet Explorer never ever gave me those messages... I also don't think that this has to do with the proxy, otherwise other programs and browsers would return the same but they don't. It's getting quite annoying and I haven't found a solution. Can this be related to anything in the prefs.js file? Any ideas?

Options: ReplyQuote
Re: http error 404 with open in bg
Posted by: Jeff
Date: November 25, 2001 04:55AM

Your proxy probably doesn't support HTTP 1.1, so you'll probably need to use HTTP 1.0 (set this in Preferences|General)

-- Jeff

Options: ReplyQuote
Re: http error 404 with open in bg
Posted by: Andres
Date: November 25, 2001 05:14AM

That did not help. I am positive that the proxy supports http 1.1, otherwise IE would not have acted properly either. Anyway, I changed the setting to 1.0 and the problem persists. It seems that the browser somehow misidentifies links (when I put the mouse on the link, it shows one address on the status line but when I click "Open in Background", the address it tries to open is something else - at least as shown on the URL bar.) This may have something to do with the K-Meleon disk cache...? (although cached data is always compared to network data).

I deleted and regenerated prefs.js with no success. Or maybe this is related to the hosts file I am using on the server?

Options: ReplyQuote
Re: http error 404 with open in bg
Posted by: Brian
Date: November 25, 2001 06:15PM

these wouldn't happen to be javascript links would they?

Options: ReplyQuote
Re: http error 404 with open in bg
Posted by: Andres
Date: November 26, 2001 10:23AM

No. Just ordinary links, like Google results etc. However, this behaviour seems to become less frequent after I reduced the memory cache from 16384 to 8192 and if I empty the disk cache at every boot and when the history plugin is turned off. That is not a final solution, of course, but it helped.

Actually a similar thing has sometimes happened with the back button: sometimes K-Meleon shows 404 Error Not Found or just a wrong page when the back button is pressed; this has happened during heavy surfing when many windows were open and the history plugin was on.

Options: ReplyQuote
Re: http error 404 with open in bg
Posted by: Jeff
Date: November 26, 2001 11:05AM

This looks like a mozilla bug:

http://bugzilla.mozilla.org/show_bug.cgi?id=100890
http://bugzilla.mozilla.org/show_bug.cgi?id=95288
http://bugzilla.mozilla.org/show_bug.cgi?id=104641
http://bugzilla.mozilla.org/show_bug.cgi?id=110139

You may want to submit a new bug directly addressing mozilla's incompatibility with your proxy. It probably wouldn't hurt to let the developer of your proxy know of this, too.

-- Jeff

Options: ReplyQuote
Re: http error 404 with open in bg
Posted by: Andres
Date: November 26, 2001 12:11PM

OK, I'll do that. Let's hope they'll fix it.

Options: ReplyQuote
Re: http error 404 with open in bg
Posted by: Andres
Date: November 27, 2001 07:38PM

The problem seemed to disappear (or at least diminish considerably) when I turned off the K-Meleon history plugin, and redirected the proxy to my ISP's cache service (so that it would not cache directly on my other home computer acting as server), changed memory cache from 16384 to 8192 KB.

Maybe changing http 1.1 to http 1.0 also helped but this alone did not make the problem disappear completely.

So I am not sure but the problem may have been related to AnalogX Proxy's caching but more probably it had to do with both the proxy and K-Meleon/Mozilla.
Anyway, everything is more or less working now.

Options: ReplyQuote


K-Meleon forum is powered by Phorum.