Search results

  1. U

    The server seems to be lying about the age of .js files in the HTTP headers.

    ...and that's what it was. Thanks, both of you.
  2. U

    The server seems to be lying about the age of .js files in the HTTP headers.

    Maybe there's a trick here I don't know about, because I know almost nothing about cache control, but from where I'm standing it looks like the server is just straight-up lying, and it's stopping things from updating in a timely manner. I noticed changes to .js files were taking quite a while...
Top