--no-cache option about static-server

[lorenmh]

@nbluis I was also encountering this issue (using static-server for development). Just submitted a pull request #32 which adds a --no-cache flag which returns the file with a 200. It doesn't modify the ETag value though

EDIT: If Etag is not edited then I think it would still cache, correct? So I updated the --no-cache option to remove the Etag header and Last-Modified header when it is enabled.

[nbluis]

Hmmm, makes sense.

Would you like to try to implement and send a pull request?

[karolk]

@nbluis this option is also incorrectly documented on the npm page: https://www.npmjs.com/package/static-server (states --no-nocache instead of --no-cache)

[nbluis]

Hi guys, thanks a lot for your help.

I decided to retire the project as I no longer have the time to maintain it.

If any of you are interested in making a fork, I'd be happy to mention it for others in the community to use.

More information about this in the README.