SOLVED! First one thing about your comment Michael. A numeric IP is necessary whenever you are using variables in the proxy path. This is because if the final string needs to be built during runtime nginx asks a resolver ro resolve the final address. And of course there is no resolver for localhost... Anyway, the solution for MY problem took quite a while. In the end I was sitting and analyzby ako673de - How to...
> > On Wed, Dec 18, 2013 at 06:27:31PM -0500, ako673de wrote: > > Found a bug in implementation of MOVE and COPY (webdav) methods. It happens if destination header contains non-ASCII characters (that need to be escaped with "%"). > I have a patch for that, would you like to try it? Well, currently I need to work around the lack of LOCK features with another WebDav sby ako673de - Nginx Mailing List - English
done. Thank you.by ako673de - How to...
Found a bug in implementation of MOVE and COPY (webdav) methods. It happens if destination header contains non-ASCII characters (that need to be escaped with "%"). An example: Rename (=MOVE) file "<www-root>/TheCore.ogm" to "<www-root>/The_Core.ogm": Request header: --> MOVE http://andinas/TheCore.ogm HTTP/1.1 --> Destination: http://andinby ako673de - Nginx Mailing List - English
Sorry, that is definitively sorted out. It IS a bug in nginx! It happens with all non ASCII characters, that need to be escaped with "%" in the request "destination" header (which is in use only by MOVE and COPY). I give you an example: Rename (=MOVE) file "<www-root>/TheCore.ogm" to "<www-root>/The_Core.ogm": Request header: --> MOVby ako673de - How to...
ako673de Wrote: ------------------------------------------------------- > And there is another bug I observed in conjunction with "Netdrive": > It's creating new folders with "MKCOL <foldername>" instead of "MKCOL > <foldername>/". nginx however is very picky with that missing "/". The > result is a "209" error ("cby ako673de - How to...
Some progress has been made: The reason for some files and folders not being displayed is a bug in PROPFIND implementation of "nginx-dav-ext-module"!!! Using the latest version in the "uri-encode" branch of their GIT-hub repository (https://github.com/semantico/nginx-dav-ext-module/tree/uri-encode) fixed that issue. But MOVE and COPY are nginx native functions and these sby ako673de - How to...
Hello, I have nginx up and running as WebDAV server on my Linux NAS. This is the server part of my nginx configuration: server { listen 443 ssl; server_name <virtualhostname>; auth_basic "Restricted"; auth_basic_user_file .htby ako673de - How to...
Forget my earlier reply! Now it works with Fritz!Box! What I did was simply to upgrade to the latest Firmware (my 7360 had a 2 year old version before), and maybe it was also helpful to enable the option "access Fritz!Box-services from outside" (even if I had to choose another port than 443 there). I don't know, but at least one of these measures helped. So, on to the next "noby ako673de - How to...
Hello out there! Still my Fritz!Box is not accessible from outside. I tried many different reverse proxy solutions, like nginx, apache, Lighty, but all of them (or just my programming skills?) failed (especially) with Fritz!Box. I know my problem is quite unique, because almost any other user simply sets a tick in the Fritz!Box menu to enable access from outside, but anyway, there must be aby ako673de - How to...
Hello, Question 1) I want my Fritz!Box configuration page being accessible from internet through a subdomain. A configuration snippet like this one server { listen 80; server_name fritz.example.org; location / { proxy_pass http://fritz.box; proxy_redirect default; }by ako673de - How to...