Finally the corruption of tech has reached a reporter at the NYT.#
I wasn't aware that Google is already marking my sites as "not secure." This really pisses me off. I worked so hard on these apps. Not for money just to make people happy.#
I just want a web browser that does its job. Browse the web. That means HTTP. You can add other protocols. But if you don't access HTTP it isn't a web browser. #
Found a problem with nodeStorage. I'm using this space to work it out. #
Here's the problem. If you go to a story on Doc Searls' 1999.io blog, it adds the port the server is running on, 1999, to the URL and redirects to it. That's because nodeStorage is not running on port 80. That's a recent thing. I used to have it running on port 80, but I needed to use PagePark for other apps running on the machine, so I moved nodeStorage to port 1999. #
What's going on. nodeStorage is doing something cool. Actually the URL that's generated by the CMS is this. When the request comes in for that address, it notices that there's a mapping from doc.blog to that sub-site, and redirects to it. It's pretty invisible, and a bit clever. I can't imagine someone else debugging this in the future and not being puzzled by it. (Hence this long comment.)#
The answer. nodeStorage needs a bit more configuration. A boolean, say flUsePortInRedirect. If you don't need us to add the port to the URL we redirect to, set this to false. To maintain backward compatibility, it defaults true.#
Now I have to implement it! I haven't updated nodeStorage in six months. I kind of don't like doing it, let a sleeping dog lie, etc. But I'm in the mood today to fix things. So here goes. #
Update: It worked the first time. Now to update the repository. Done. #
