prologue uses more memory per request for static files
If serving a static image via img tag or especially a video via html5 video tag, prologue uses more and more memory per request. With a video in the page, you can quickly be using 1GB of ram.

This also happens with other nim web frameworks, so it's likely something to do with the underlying http server implementations.

However, this is easily mitigated by using nginx in front of prologue as a reverse proxy, and specifically, by explicitly serving the static files with nginx via a location block as demonstrated below.

```
server {
    server_name prologue-test;

    location ^~/static/ {
	root /var/www/prologue-test;
	try_files $uri $uri/ ;
	expires 1y;
	access_log off;
    }

    location / {
	proxy_pass http://localhost:8080;
	proxy_set_header Host $host;
	proxy_set_header X-Real_IP $remote_addr;
    }

}
```
If testing on localhost, you will want to create a line in /etc/hosts for the server_name you are using in your nginx config, and use an env variable for the host name in your app's urls, so that all your static resources use that domain/server name instead of localhost:8080. Otherwise, the requests would bypass nginx and be served by prologue.

Please note that the above nginx config is a minimal example and should not be considered complete for production use, as you will need an http block with various settings for performance and security, and likely other lines in this server block. The example above is just to demonstrate the part related to this workaround.