socketstream/socketstream — pull request #290 by drosen0 (2012-08-30 16:56:42+00:00)
Title: Character encoding should appear earlier in the HTML

Some browsers apparently pre-parse the first 1kB of HTML to try to find the character encoding, before trying to guess what it is. [Relevant section of HTML5 draft spec](http://www.w3.org/TR/html5/parsing.html#determining-the-character-encoding).

In development mode, with a large number of client scripts, the SocketStream header output can be large. This can push the `` so it is outside of the first 1kB of the file. Firefox generates this message, which can be seen in FireBug:
> The character encoding declaration of the HTML document was not found when prescanning the first 1024 bytes of the file. When viewed in a differently-configured browser, this page will reload automatically. The encoding declaration needs to be moved to be within the first 1024 bytes of the file.

This would never be an issue in production mode, since the assets are packed, so this is a pretty unimportant change.