JDPFu.com 2025

We’re on Port 80 Now

Most of you probably don’t care, but this website underwent some big changes today. We are running on port 80 now. For the last 3 years, this blog has run on port 82, which caused some problems for some corporate access where the network admin was too lazy to proxy based on protocol and only proxied based on port. Those people couldn’t access the site.

Going forward, please use http://blog.jdpfu.com/ to access the site. Nothing under that should change, in theory.

We added port 80 as a way to allow access to the blog. We didn’t stop port 82 access so that old links from external locations will continue to work, but slowly, over time, access via port 82 should go away. Initially, port 82 will only have 1 server listening with port 80 getting 4 servers. For faster performance go to port 80.

What should you do?

1. You should update your RSS reader from jdpfu.com:82/articles.rss to http://blog.jdpfu.com/articles.rss
2. Anytime you see :82 in a URL, don’t worry, provided it works. If it doesn’t work, try removing the :82 part. That shouldn’t be necessary, but you never know. http://blog.jdpfu.com/ should be the subdomain that http://jdpfu.com/ redirects to from now on, at least from the top page request.

When you have lots of servers, things can get complicated.

If you see problems, please drop a comment to us.

We run lots of internal only web servers that also listen on port 80, so some of these services could be confused at the reverse proxy server and redirect to the wrong place. Hopefully, it doesn’t become a big issue for the public users. You guys should have priority.

In a few months, we may setup an apache server for port 82 that handles the rewrites automatically and provides a permanently moved error as part of the redirect. Perhaps next week. Perhaps.