This upgrade is probably only interesting to the geeks in the crowd.

When generating the HTTP response headers before displaying a journal, the system can optionally provide a Content-Length header specifying how large the document is in bytes. It generally isn't neccessary because browsers and such can figure it out on their own.

However, we have been noticing some problems with user connections in recent weeks and so I have added that Content-Length header to make it explicit to the browser how much data it is supposed to read before it is done.