madness behind a proxy

[bodsch]

I configured a madness service behind a proxy with additional route /doc (http://proxy/doc)

madness redicted the request back to / (also missing my proxy route)

curl -v http://localhost/doc/index.md
*   Trying 127.0.0.1...
* TCP_NODELAY set
* Connected to localhost (127.0.0.1) port 80 (#0)
> GET /doc/index.md HTTP/1.1
> Host: localhost
> User-Agent: curl/7.53.0
> Accept: */*
> 
< HTTP/1.1 302 Found 
< Server: nginx/1.10.2
< Date: Thu, 16 Mar 2017 18:18:04 GMT
< Content-Type: text/html;charset=utf-8
< Content-Length: 0
< Connection: keep-alive
< Location: http://localhost/index
< X-Xss-Protection: 1; mode=block
< X-Content-Type-Options: nosniff
< X-Frame-Options: SAMEORIGIN

it is possibility to configure a proxy-route into madness?

[DannyBen]

It was not designed for that use case, no. It is expected to run where its documents are served from the root URL.

This is the actual server code

I believe you should be able to configure it to be available at something like http://subdomain.proxy/

Also, you do not need to request the index.md file. I suggest you first test it and configure it with a basic configuration, see that it works, and then try to add the proxy.

[bodsch]

sorry, in my current use case is this possible. :(
i look around in your code. i hope i find a resolution for my problem, than comes a PR ;)

[DannyBen]

I am closing this. If there is a reason to keep it open, let me know.