Plone's webdav and NGINX?

[Johannes Graumann]

After reading up on this it seems likely that this is a limitation due to 
the subset of webdav commands that are implemented in NGINX. Is work planned 
to extend that subset?

Sincerely, Joh

Johannes Graumann wrote:

> Hi,
> 
> I have the following setup running:
> 
> server {
>   listen   8443;# Custom port as the standard 443 is taken by kolab
>   server_name  www.graumannschaft.org h1616679.stratoserver.net;
>   # SSL is using KOLAB generated credentials
>   ssl  on;
>   ssl_certificate  /kolab/etc/kolab/cert.pem;
>   ssl_certificate_key  /kolab/etc/kolab/key.pem;
>   ssl_session_timeout  5m;
>   ssl_protocols  SSLv3 TLSv1;
>   ssl_ciphers  ALL:!ADH:!EXPORT56:RC4+RSA:+HIGH:+MEDIUM:+LOW:+SSLv3:+EXP;
>   ssl_prefer_server_ciphers   on;
>   location / {
>     proxy_pass
> 
http://localhost:8080/VirtualHostBase/https/h1616679.stratoserver.net:8443/GraumannschaftPlone/VirtualHost$
>   }
> }
> 
> I am now trying to make plone's webdav capabilities available through
> nginx and added
> 
>   location /dav/ {
>     proxy_pass
> 
http://localhost:1980/VirtualHostBase/https/h1616679.stratoserver.net:8443/GraumannschaftPlone/VirtualHost$
>     dav_methods  PUT DELETE MKCOL COPY MOVE;
>     create_full_put_path    on;
>     dav_access      user:rw;
>   }
> 
> When attempting to mount that location through davfs, I get properly asked
> for user an password, but the resulting mountpoint remains empty (just
> "lost+found" is present).
> I started to read u and am wondering whether this is a limitation rooted
> in nginx's limited webdav support or whether I am doing something
> generally wrong ... any input is highly appreciated. Thanks for your time,
> 
> Joh
> 
> 
> 
> _______________________________________________
> nginx mailing list
> nginx at nginx.org
> http://nginx.org/mailman/listinfo/nginx