Actions
Feature #8748
closedAllow per-plugin enablement of HTTP in configuration files
Description
For example, one may want to only enable unauthenticated access to the templates plugin, while still restricting the rest of the plugins to SSL.
Updated by The Foreman Bot almost 10 years ago
- Status changed from New to Ready For Testing
- Pull request https://github.com/theforeman/smart-proxy/pull/241 added
- Pull request deleted (
)
Updated by Anonymous almost 10 years ago
- Status changed from Ready For Testing to Closed
- % Done changed from 0 to 100
Applied in changeset 59846579172d655e6021b744f5e23a4ccf77e734.
Updated by Dominic Cleal almost 10 years ago
- Assignee set to Greg Sutcliffe
- Translation missing: en.field_release set to 28
Updated by Dominic Cleal over 9 years ago
- Related to Bug #8990: foreman_proxy puppet module should be aware of new plugin http/https settings added
Updated by Stephen Benjamin over 9 years ago
- Blocks Feature #8991: Support templates plugin in Capsule added
Actions