-
Notifications
You must be signed in to change notification settings - Fork 239
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Appended allowRemoteCacheManagement key into web.config to allow remote cache management (clear cache). #59
Conversation
[ReleasePrep 2018-02-26]Merge dev into master
…te cache management.
…low remote cache management." This reverts commit daf5b2d.
…te cache management.
…te cache management.
…low remote cache management." This reverts commit daf5b2d.
…te cache management.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@ezverev Sorry for the delay in response!
If you can address the web.config
feedback, I think we should merge your contribution. Thanks!
src/NuGet.Server/Web.config
Outdated
@@ -69,6 +69,8 @@ | |||
on a fixed 1-hour interval. | |||
--> | |||
<add key="enableFileSystemMonitoring" value="true" /> | |||
<!--Set allowRemoteCacheManagement to true to enable the "clear cache" and other cache operations initiated via requests originating from remote hosts.--> | |||
<add key="allowRemoteCacheManagement" value="true" /> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would set default to false
, to match the default in code and existing behavior.
I've made the requested change. |
Verified - build 39649 |
In smaller companies it is important to have an ability to enforce quick nuget updates. I suggest allowing the cache management be available for remote users via config.