ArtemGr <artemciy@...> writes:
> Problem using the proxy with a custom port:
>
> <mapurl>
> <url>^/(.*)$</url>
> <target>proxy <at> tntnet</target>
> <args><arg>http://myhost:12080/$1</arg></args>
> </mapurl>
>
> gives "Error/Not Found", whereas
>
> <mapurl>
> <url>^/(.*)$</url>
> <target>proxy <at> tntnet</target>
> <args><arg>http://myhost/$1</arg></args>
> </mapurl>
>
> works.
>
> I'd think custom ports are important if tntnet to be used as a front-end:
> there's often several back-ends working on different ports.
After some experimentation with tntnet proxy I've figured
that the "$1" is not supposed to be there,
since proxy always adds the current path into the url anyway:
url += request.getPathInfo();
Also, the proxy is currently broken for me because
std::string url = uri.path();
url += request.getPathInfo();
produces a double-slash when getting the root page (e.g. http://myhost/),
turning http://myhost/ into http://myhost//.
Here is a patch fixing some of these: https://gist.github.com/2987769
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Tntnet-general mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/tntnet-general
