WebDAV behind hiawatha Reverse Proxy
krabbl
8 April 2016, 19:44
Hi,
we are trying to use hiawatha as reverse proxy for a websvn like application, which relys on webdav. The access via browser is working fine, but all actions like commits etc. are resulting in a '504 Gateway Timeout'. Is there a way to get this working?
Almost the same behavior as mentioned here:
https://stackoverflow.com/questions/1110710/webdav-behind-a-reverse-proxy
Thanks in advance.
Regards
Hugo Leisink
10 April 2016, 18:11
Perhaps the uploads are larger than allowed? Try the MaxRequestSize setting.
Krabbl
10 April 2016, 19:17
We tried this already, including disabling all features like SQLi prevention etc. (which should indeed have nothing to do with this).
The reverse proxy (hiawatha) is configured as:
ReverseProxy .* https://192.168.0.1
The websvn server is an apache, which is working when not using reverse proxy. The only which works with the reverse proxy is accessing the website, but trying to check out with an svn client leads to the error below.
access.log:
ip-client - - [date] "OPTIONS /svn/example HTTP/1.1" 401 1288 "-" "SVN/6.6.6 (os) serf/6.6.6"
ip-client - - [date] "OPTIONS /svn/example HTTP/1.1" 200 1601 "-" "SVN/6.6.6 (os) serf/6.6.6"
ip-client - - [date] "OPTIONS /svn/example HTTP/1.1" 504 1929 "-" "SVN/6.6.6 (os) serf/6.6.6"
error.log:
date|Reverse proxy timeout for 192.168.0.1
Do you know if there has some rewrite rule to be applied ... like mentioned here [1]?
[1] http://silmor.de/proxysvn.php
Hugo Leisink
10 April 2016, 20:12
I don't know SVN, so I don't know if it needs some URL rewriting rule.
Krabbl
13 April 2016, 11:10
The problem is related to subversion, which uses nowadays http chunked requests (setting this clientside to no helps, but disables default behaviour). Do you have an idea or is there in option in hiawatha to deal with this?
Hugo Leisink
16 April 2016, 07:59
I don't know what goes wrong. I don't know subversion and how it sends it HTTP requests.
This topic has been closed.