Any Port in a Storm
June 24, 2004
For a long time this blog, the wiki, and miscellaneous, other files have been accessible through a lovely bit of complication: (936)
- Incoming HTTP requests came in on port 8000 to an old rickety Linux box that was due to be removed ages ago and was so rusty and weird that I dare not touch it. As in ip forwarding was not an option and changing the apache config seemed more than I could bear. And doing special magic for a variety of special friends. (937)
- In inetd, netcat proxied port 8000 at that old machine to port 80 on a newer machine. That machine was configured so that any URLs it generated appeared to be for port 8000 on the other machine. (938)
It was one of those I'll get to that any day now situations that started more than a year and a half ago. (939)
Last night was finally that day. The newer machine is now out on the boundary, listening on both ports 80 and 8000. If you prefer your urls 5 characters shorter feel free to remove the :8000, things will still work. (93A)
Things will probably be a bit faster, and now there will actually be useful information in the logs. (93B)
Sending...
Comments
Yay. Again, sorry for the confusion last night, re: some assistance / peanut gallery type stuff. (93C)
Hello. If you are owner of this site, delete this message, please. (OPT)
bairontechnologiesforall bairontechnologiesforall http://www.bairontechnologiesforall.biz (OPU)