Skip to content
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

Leave require directive unmanaged #1267

Merged
merged 1 commit into from
Nov 18, 2015

Conversation

robertvargason
Copy link
Contributor

Instead to default require to 'Require all granted' if no 'require'
parameter is set for a directory, leave require unmanaged in apache 2.4
if needed. This is useful for complex authentication/authorization
requirements which are handled in a custom fragment.

'path' => '/var/www/files_nrag',
'provider' => 'files',
'require' => 'unmanaged',
},
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this seems needlessly duplicated, and is unused

Instead to default require to 'Require all granted' if no 'require'
parameter is set for a directory, leave require unmanaged in apache 2.4
if needed. This is useful for complex authentication/authorization
requirements which are handled in a custom fragment.
igalic added a commit that referenced this pull request Nov 18, 2015
@igalic igalic merged commit 57c0a18 into puppetlabs:master Nov 18, 2015
@igalic
Copy link
Contributor

igalic commented Nov 18, 2015

thanks @robertvargason!

@ubellavance
Copy link

Thanks for this PR, I spent a lot of time searching to find how not to have the 'Require all granted' in my Limit block. Would there be a better way to document it?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants