149500 - Mozilla remembers trailing slash after redirect to directory URL

Status: RESOLVED INVALID

(SeaMonkey :: Location Bar, defect)

Description

[John Belmonte]

Mozilla gets into a situation where it forces a URL like http://xxx.xxx/foo/
even though you enter (and require) http://xxx.xxx/foo.

Steps to reproduce:

    1) get a web server running Apache that you can upload to
    2) make a test directory on the server:
        mkdir slashtest
    3) make sure the Indexes and MultiView options are enabled in the test
directory.  For example in .htaccess:
        Options +MultiView +Indexes
    4) make a subdirectory in slashtest:
        mkdir goofy
    5) in Mozilla, enter a URL to the subdirectory *without* the trailing slash:
        http://xxx.xxx/slashtest/goofy

Step 5 will result in a redirect to http://xxx.xxx/testdir/goofy/.  From here
Mozilla will always append the trailing slash when it is omitted.  To
demonstrate why this is a problem:

    6) remove the subdirectory:
        rmdir goofy
    7) make a content file with the same name:
        echo hello > goofy.txt
    8) from Mozilla try to go to the URL without use of the file name extension
(note that it is common to omit MIME extensions from URL's when making use of
content negotiation): 
        http://xxx.xxx/slashtest/goofy

In step 8, instead of the client seeing the contents of goofy.txt, the server
will return a Not Found because Mozilla converted the URL to
http://xxx.xxx/slashtest/goofy/.

Konqueror and Internet Explorer do not have this behavior.


Version info:
    Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0rc3) Gecko/20020531
Debian/1.0rc3-2

Comment 1

[Christian :Biesinger (don't email me, ping me on IRC)]

-> URL bar

Comment 2

[Michiel van Leeuwen (email: mvl+moz@)]

(note: it should be MultiViews in .htaccess)

I tried, and could repro.
BUT: apache sends a "301 Moved Permanently" when accessing the goofy dir. So
mozilla should rememeber that goofy -> goofy/ 
So this seems intended behaviour to me.

Comment 3

[Alexander Opitz]

@reporter

Does it happens on newer builds?
I think so ... cause the 301 will be cached.

Comment 4

[Alexander Opitz]

Since over 1 month no answer from the reporter, so closing bug as invalid.

Comment 5

[John Belmonte]

Sorry I wasn't familiar with the "@reporter" lingo.  I left careful instructions
on how to reproduce the bug and don't see why it should be my responsibility to
check the bug against new versions.

No, the bug does not seem to be present in 1.4.