IMHO this is fixed with Release 0.2.0.
My previous comment should have said rev. 26, not 22.
Fixed with rev. 22. The problem was that the remote server used HTTP/1.1 in its response and chunked transfer encoding but the inteproxy said HTTP/1.0 in its response to the client but kept the chunked encoding. chunked is not allowed in 1.0.
Björn was right. inteproxy-demo.intevation.org is only available through a proxy. Setting https_proxy solved that.
Yes, the server is listening. May be you have to set this ... export https_proxy=http://HOST:PORT/
I just tried to test this. Is the server actually listening on the https port currently? I get "connection refused". Also, which username/password should I use to access the server at inteproxy-demo.intevation.org/cgi-bin/frida-wms?
