New beta plugin: WebDAV (WebFolders)

[ghisler(Author)]

No, Google mail does not support WebDAV connections, sorry. Other free mailers like the German GMX do.

[octane]

Hi Christian,

habe gerade ein "Bug" festgestellt:

Wir haben hier ein Zwangsproxy, der leider die Inhalte (wir greifen auf die HTTPS-Version von GMX zu) zwischenspeichert. Wir hatten hier eben den Fall, dass wir die gleiche Datei 2x heruntergeladen haben und es kam 2x die gleiche Datei an, obwohl sie mittlerweile von andere Stelle neu hochgeladen wurde. Die Datei hat sich also auf dem Server geändert.

Ein temporärer Workaround ist, das wir vor dem Download STRG+R drücken, um die Directory neu zu laden.

Beim Request sollte der Headereintrag: "If-Modified-Since: <aktuelles Datum>" mitgesendet werden, dann ignoriert der hier vorhandene Proxy den Cache.

Grüße,
octane

[ghisler(Author)]

(Reply in English so everyone can understand it)

I don't think that "If-Modified-Since" is the right key here.

The If-Modified-Since request-header field is used with a method to make it conditional: if the requested variant has not been modified since the time specified in this field, an entity will not be returned from the server; instead, a 304 (not modified) response will be returned without any message-body.
See http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html

So if the WebDAV plugin sends this header, and the file has not been modified, the server just returns 304 Not Modified and no document.

Actually a good proxy should implement this header, not the client! The proxy needs to send a request with this parameter, and if the file hasn't changed, return the unchanged document from the cache to the client - otherwise the changed one.

What may help is a header like
Proxy: no cache

Or maybe there is a header to instruct the proxy to re-validate the data via a not modified request?

[octane]

Or maybe there is a header to instruct the proxy to re-validate the data via a not modified request?

I dunno. I only know, that the "If-Modified-Since"-header sent by client behind the proxy get the correct (newer) files. It seems, that the proxy is buging.

[tosbsas]

Sorry, but I have problems with connecting to 1und1 webspace

I have the ftp user and the password, but it keeps saying 401 unauthorized

Anyone who can help me??

Ruben

[ghisler(Author)]

A quick google search for
1und1 webdav
reveals that you need to connect to https://mediacenter.1und1.de

See:
http://faq.1und1.de/access/internet_profi_faq/features/mc/2.html

[tosbsas]

ok, but doesn't work either. With my normal user name and passowrd I get error 401

with ftp username and password I get cannot resolve hostname - seems to load 30%

Ruben

[tosbsas]

but with IE it does not work either - wierd

Ruben

[Jojo]

Is anybody using this plug-in with buzzsaw webfolders (Autodesk)? Not sure what technology they are using on their servers, but I have some issues with it.

I can upload files to the server but can't delete them, I also can't create folders.

Both operations are working fine, when I use the webfolders through My Network Places in Windows.

Thanks for any tips.

[Diam0nd]

Hi,

my photo service Smugmug just introduced a WebDAV-interface. It's still in testing phase and read only so far.
It works with the Explorer, but not with the TC plugin.

I can view the root directory which includes all my categories, but when I enter a category-directory, I just get a list with an unamed folder "[]"

Here's my log file (I just removed the cookie):

Code: Select all

CONNECT \Smugmug
Get dir: /smugdav.mg
PROPFIND /smugdav.mg/ HTTP/1.1
Depth: 1
Content-Type: text/xml; charset="utf-8"
User-Agent: ezdavplugin
Host: upload.smugmug.com
Content-Length: 0
Connection: Keep-Alive
Cache-Control: no-cache
Cookie: smstatus=10.27.27.13.1106942958156586; SMSESS=[deleted]; res=
******Received headers
HTTP/1.1 207 Multi-Status
Date: Fri, 28 Jan 2005 22:33:42 GMT
Server: Apache
X-Powered-By: smugmug/1.1.0
Set-Cookie: SMSESS=[deleted]; path=/; domain=.smugmug.com
Cache-Control: private, max-age=1, must-revalidate
Pragma:
X-Dav-Powered-By: smugDAV/0.0.1
X-We
207 Multi-Status
Get dir: /smugdav.mg\C0_Other
PROPFIND /smugdav.mg/C0_Other/ HTTP/1.1
Depth: 1
Content-Type: text/xml; charset="utf-8"
User-Agent: ezdavplugin
Host: upload.smugmug.com
Content-Length: 0
Connection: Keep-Alive
Cache-Control: no-cache
Cookie: smstatus=10.27.27.13.1106942958156586; SMSESS=[deleted]; res=
******Received headers
HTTP/1.1 207 Multi-Status
Date: Fri, 28 Jan 2005 22:33:46 GMT
Server: Apache
X-Powered-By: smugmug/1.1.0
Set-Cookie: SMSESS=[deleted]; path=/; domain=.smugmug.com
Cache-Control: private, max-age=1, must-revalidate
Pragma:
X-Dav-Powered-By: smugDAV/0.0.1
X-We
207 Multi-Status

What could be wrong? Could there be a server problem? If yes, what should I tell the smugmug guys?

Thanks for your help and the great plugin (much faster than the Explorer, as usual),
Sebastian

Any luck getting that plugin to work with SmugMug? I can't even log in. Any chance you could tell me the settings you are using?

[ghisler(Author)]

I don't see any kind of error in your log. Please turn on extended logging in the plugin connect dialog. While connected, the plugin should then keep the last received directory listing in your TEMP directory. Please post its contents here.

[nidecta]

I got an error like this,what should I do.

--------------------
PROPFIND / HTTP/1.1
Depth: 1
Content-Type: text/xml; charset="utf-8"
User-Agent: ezdavplugin
Host:
Content-Length: 0
Connection: Keep-Alive
Cache-Control: no-cache
******Received headers
HTTP/1.1 501 Method PROPFIND is not defined in RFC 2068 and is not supported by the Servlet API
Date: Sat, 15 Aug 2009 02:08:02 GMT
Server: Apache
Cache-Control: private
Expires: Thu, 01 Jan 1970 09:00:00 JST
Set-Cookie: JSESSIONID=FDA778B059AA554ADA2E69AF06DB5212; Path=/.dx; Secure
Content-Length: 1383
MS-Author-Via: DAV
Connection: close
Content-Type: text/html;charset=utf-8
Error: HTTP/1.1 501 Method PROPFIND is not defined in RFC 2068 and is not supported by the Servlet API
Disconnected

[ghisler(Author)]

Your server doesn't support WebDAV, or the WebDAV module isn't installed. for example, Apache requires a module for WebDAV.

Some servers also don't allow WebDAV over HTTP - you need to check the option "secure connection (via SSL)".

[ghisler(Author)]

I have now created a new version of my WebDAV plugin which uses the same new functions as the SFTP plugin to support multiple proxies. It also retains compatibility with existing proxy settings. The advantage is that you can quickly change the proxy of all connections using the same proxy, e.g. when changing between home and work PC.

Please download the new version 2.2 beta 1 from here:
https://plugins.ghisler.com/beta/webdav_22_beta1.zip
and the sources:
https://plugins.ghisler.com/beta/webdav_src22_beta1.zip

This new version also allows to store the proxy password in the internal password manager of Total Commander (protected with master password).

Please let me know here in the forum or by e-mail whether it works or not!

[WonkoTheSane]

Hi,

I've granted a couple of my friends WebDAV access to my NAS, which
is a QNAP TS-410. As far as I know the webserver is based on apache.

This is working without a problem for the clients running Windows 7.

One of my friends however is still running on vista and he's unable to
download larger files (a couple of gig in size).

Here's the log:


Get dir: **************************
HTTP error: Zertifizierungsstelle ist ungültig
HTTP error: Zertifikatsname CN ist ungültig
PROPFIND ******************** HTTP/1.1
Content-Type: text/xml; charset="utf-8"
Depth: 1
User-Agent: ezdavplugin
Host: *********************
Content-Length: 0
Connection: Keep-Alive
Cache-Control: no-cache
******Received headers
HTTP/1.1 207 Multi-Status
Date: Tue, 28 Jun 2011 08:34:39 GMT
Server: Apache
Keep-Alive: timeout=15, max=99
Connection: Keep-Alive
Transfer-Encoding: chunked
Content-Type: text/xml; charset="utf-8"
207 Multi-Status
=================
File receive:***************************************
HTTP error: Error 12153, FormatMessage error 15105
=================
File receive: ************************************
HTTP error: Error 12153, FormatMessage error 15105


Thanks in advance for your help,

Matthias