136213 - URL without explicit file reference is not found

Status: RESOLVED DUPLICATE of bug 76431

(SeaMonkey :: General, defect)

Description

[Kirk Parsons]

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:0.9.8) Gecko/20020204
BuildID:    2002020406

When I type in an URL field without an explicit file reference in the URL I get
the following error message: "The file /start/ cannot be found. Please check the
location and try again."

I also get the same message when I try the following URL (which is behind the
Netscape firewall):

http://horror.netscape.com:8080/ComponentRelease

The interesting thing about the URL above, is that if I put a trailing slash on
it, as in:

http://horror.netscape.com:8080/ComponentRelease/

It finds the index.html file in the ComponentRelease directory.

I have to imagine that someone has reported this previously, since I run into
this a lot (it affects many of my bookmark URLs), but searched for a while, and
wasn't able to find an identical bug.




Reproducible: Always
Steps to Reproduce:
1.Go to:  http://www.mozilla.org/start
2.Receive "file not found" message.


Actual Results:  1.Go to:  http://www.mozilla.org/start
2.Receive "file not found" message.

Expected Results:  1.Go to:  http://www.mozilla.org/start
2.URL comes up properly

I'm calling this "major", since it's the address bar that is broken.  OTOH, if
there's something specific to my install that makes this happen, than that would
make it less severe.  I'd really like to hear if this happening to other people,
or if there's already been a bug filed on this (which I would hope, and I'd also
then hope that  it's already tagged nsbeta1+, and will get fixed with Mozilla 1.0).

Comment 1

[Matthias Versen [:Matti]]

Reporter: 
Do you use two instances of mozilla ?
(Run Mozilla and NS6.x at the same time with the same profile ?)

Comment 2

[Matthias Versen [:Matti]]

hit too early commit :-)

This can corrupt your cache and you must clear the Disk Cache.

Comment 3

[Kirk Parsons]

Indeed I do sometimes run Mozilla and NS6.x at the same time.  So, if I clear my
cache, and avoid running the two versions simulataneously, I can avoid this
problem in the future?  Or, rephrased, if I am careful to exist the NS6.x before
starting up Mozilla 0.9.x (and vice versa), this would avoid the problem?

Comment 4

[Matthias Versen [:Matti]]

yes, this should avoid the problem


*** This bug has been marked as a duplicate of 76431 ***

Comment 5

[Kirk Parsons]

Sorry to file the duplicate, but thanks much for the quick resolution on this!