Bug 486154 - konqueror fails to access files via webdav correctly
Summary: konqueror fails to access files via webdav correctly
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Fedora
Classification: Fedora
Component: kdebase
Version: 10
Hardware: i686
OS: Linux
low
medium
Target Milestone: ---
Assignee: Than Ngo
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-02-18 17:16 UTC by dhawes
Modified: 2009-03-17 01:48 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-03-17 01:48:51 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
Picture of error message (98.25 KB, image/png)
2009-02-18 17:18 UTC, dhawes
no flags Details


Links
System ID Private Priority Status Summary Last Updated
KDE Software Compilation 184923 0 None None None Never

Description dhawes 2009-02-18 17:16:55 UTC
Description of problem:

This version of konqueror is failing to including a trailing slash in webDAV collection URIs. Apache redirects as per standard and the user receives a 301 error when attempting to access directories.


Version-Release number of selected component (if applicable):

kdebase-4.2.0-2.fc10.i386

How reproducible: very


Steps to Reproduce:
1.upload files to a web server using webdav
2.connect to them using konqueror and try to delete one of them
3.
  
Actual results:

error message:

 (see attached png)

 An unexpected error (301) occurred while attempting to retrieve the contents
of the specified file or folder.


Expected results:
It should delete the file.

Additional info:

Comment 1 dhawes 2009-02-18 17:18:27 UTC
Created attachment 332420 [details]
Picture of error message

Comment 2 Rex Dieter 2009-02-18 17:27:39 UTC
An excellent candidate to report to upstream developers @ bugs.kde.org.   Mind doing so?

Comment 3 dhawes 2009-02-19 11:05:54 UTC
Submited as bug 184923 @ bugs.kde.org

Comment 4 Steven M. Parrish 2009-03-17 01:48:51 UTC
Thanks for reporting upstream, will monitor for resolution of this issue


Note You need to log in before you can comment on or make changes to this bug.