Added cache-control to nginx serving and forwarded Etags
Warning:
  In my tests using
    curl http://localhost/ -I
  I get the Etag
  Using
    curl http://localhost/ -I --header "If-None-Match: etag_from_previous_request"
  I get 304 Content not modifyed (as expected)

  Why then is it that chrome and firefox WONT USE THE ****ING ETAGS!!!!
  They completely ignore the etag through nginx, they do not appear in the response header,
  but using localhost:6543 directly they are fine.
  WTF!!!
Technically the etag field is ETag and not Etag
It appears that waitress is outputting
  'Etag' using `curl http://localhost:6543/`
yet
  `curl http://localhost/ext/jquery.min.js` outputs 'ETag'
I checked the pyramid stack and it appears like the etag is correctly set as ETag.
I'm unsure of where in the chain it is getting converted to 'Etag'

I think nginx is getting confused with the case

My next idea is to blow away all my python libs and build env again just in case the issue is a bug with waitress/pyramid
After that, could I use nginx to perform a rewrite rule?
Corrected inconsistent indentation