Closed brianmcmichael closed 8 years ago
@ericfranz please review.
npm install <package> --save
option still updates all of the other dependencies as long as they are in the version range specified in the package.json
. I'm not sure that there's a way around that short of hardcoding precise version numbers into the package.json of OSC/cloudcmd, which I don't like the idea of.We may need to later remove no-store from "Cache-Control" headers per the above, but for now it's working without the modification.
Why would we need to do this? Can we remove it right now? Does cache busting still work?
Why would we need to do this?
It's part of the instructions for getting FontAwesome to work with IE. We're using IE and HTTPS though. See: https://github.com/FortAwesome/Font-Awesome/wiki/Troubleshooting#im-hosting-fonts-on-my-server-and-icons-dont-show-up
Can we remove it right now?
Sure. I made the smallest cut to get this working.
Does cache busting still work?
The "Cache-Control" headers are still in place. "Pragma" is part of HTTP/1.0 specification, while "Cache-Control" is HTTP/1.1
no-store
from "Cache-Control" headers per the above, but for now it's working without the modification.