Nginx not serving updated files

[alystair]

Was directed here by @cretueusebiu - maintainer of the Windows port of Valet. Copy of the issue I submitted to his repo @ cretueusebiu#88

Sometimes Nginx does not recognize files have been modified, as such browsers reload from disk cache - since Valet is a development environment wouldn't it make sense to specifically disable caching mechanisms?

Nginx is specifically returning cache tags in response headers

Date: Sat, 02 Jun 2018 19:29:15 GMT
ETag: W/"5b1126c5-4a3"
Last-Modified: Fri, 01 Jun 2018 10:58:13 GMT

[drbyte]

You didn't state what "kinds" of resources were particularly troublesome in this context.

I haven't run into any situation where this was an issue that seemed to be needing fixing.
ie: when dealing with resources that are likely to be cached by the browser it's been normal "muscle memory" to ask the browser for a refresh.

The default nginx configs in valet are pretty generic, and don't touch any defaults related to caching (save for enabling gzip, which can influence the strength of ETag value matching).

So, if you wish to customize it, note a simple trick with Valet:
All the ~/.config/valet/Nginx/*.* files get loaded inside the nginx http config section, which means you could drop a cache-dev.conf file in there with any directives you want for disabling caching.

[drbyte]

I believe this can be closed.