Description of problem:

The http: handlers take the URL quoted, remove the trailing "/" (wrong for http and
iffy for dav) and issue a PROPFIND. Apache DAV replies with a 301 content
redirection message which the DAV detection then treats as a "no DAV" error. It
then retrieves the 
URL via GET and sees a redirect message. It then fetches the redirected URL  **BUT**
displays the redirection URL text not the correct URL text.

How reproducible:
100%

Steps to Reproduce:
1. Set up a DAV subdirectory on apache
2. Try and use nautilus with it
3.  Now try using the KDE file manager with it to prove its a client side bug
    
Actual results:
For https:// nautilus doesn't support it at all
For http:// the behaviour described is seen
With KDE or Windows systems accessing the same DAV folder it just works. Ditto
with davfs2.

Expected results:
Working DAV

Additional info:
This problem doesn't show up with the Microsoft DAV server side as it replies to
the PROPFIND without issuing a redirect.

As a footnote it seems the whole http:// support is rather buggy - I've also had
nautilus crashes while trying to debug this. I may have a look at writing a
proper dav: VFS module using neon, since neon already provides 99% of the needed
code including SSL.

Regardless of that the redirect bug needs fixing - it shouldnt treat redirect as
a propfind test failure and it shouldnt show the wrong page. It probably
shouldnt trim the trailing "/" either.