What's new?
- Minor release has out.- Reload conf on start if htoven is already running
- Bind to specific interface with -i
- Code refactored a bit
htoven.org.ua
Print Version
Mailform
Last update:
May 14. 2009 01:58:14
Main > About
Everything has began, when I connected my two machines behind NAT through SSH tunnel to public server with real IP. They could be accessed like that: someserver.com:3000, someserver.com:3001. For internal needs it is OK. But I like when everything is beautiful, like one.someserver.com and two.someserver.com (or even one.com and two.com - you just need to have domain name).
So when you request coolpage.com HTOveN will check it's config file and tunnel your connection to, say, 192.168.0.167:8080 where coolpage.com is hosted. It is transparent to end user, who doesn't know where real HTTP daemon is running.
It is written for Linux/POSIX with C. Stripped x86 binary is 13 572 bytes. I guess it would be nice to embed into some SOHO routers to publish few internal servers using standard 80-th port for everyone binded to single real IP. (port forwarding will work for one internal web-server only, if you want to use 80 port for every web server to avoid addersses like host.com:1234 you should use HTOveN)
About
Everything has began, when I connected my two machines behind NAT through SSH tunnel to public server with real IP. They could be accessed like that: someserver.com:3000, someserver.com:3001. For internal needs it is OK. But I like when everything is beautiful, like one.someserver.com and two.someserver.com (or even one.com and two.com - you just need to have domain name).
So when you request coolpage.com HTOveN will check it's config file and tunnel your connection to, say, 192.168.0.167:8080 where coolpage.com is hosted. It is transparent to end user, who doesn't know where real HTTP daemon is running.
It is written for Linux/POSIX with C. Stripped x86 binary is 13 572 bytes. I guess it would be nice to embed into some SOHO routers to publish few internal servers using standard 80-th port for everyone binded to single real IP. (port forwarding will work for one internal web-server only, if you want to use 80 port for every web server to avoid addersses like host.com:1234 you should use HTOveN)