Re: [users@httpd] Block access to "OPTIONS *"

2016-02-12 Thread Yann Ylavic
On Fri, Feb 12, 2016 at 1:29 PM, Daniel Gruno wrote: > On 02/12/2016 01:28 PM, Jim Jagielski wrote: >> Blocking OPTIONS has a long and illustrious history... >> I am -0 on doing anything more related to it ;) >> > > Isn't that why we have the optional mod_allowmethods these days anyway... That lo

Re: [users@httpd] Block access to "OPTIONS *"

2016-02-12 Thread Yann Ylavic
On Fri, Feb 12, 2016 at 1:28 PM, Jim Jagielski wrote: > Blocking OPTIONS has a long and illustrious history... > I am -0 on doing anything more related to it ;) OK, I see, let's users@ play with the workaround then :)

Re: [users@httpd] Block access to "OPTIONS *"

2016-02-12 Thread Daniel Gruno
On 02/12/2016 01:28 PM, Jim Jagielski wrote: > Blocking OPTIONS has a long and illustrious history... > I am -0 on doing anything more related to it ;) > Isn't that why we have the optional mod_allowmethods these days anyway... With regards, Daniel.

Re: [users@httpd] Block access to "OPTIONS *"

2016-02-12 Thread Jim Jagielski
Blocking OPTIONS has a long and illustrious history... I am -0 on doing anything more related to it ;)

Re: [users@httpd] Block access to "OPTIONS *"

2016-02-12 Thread Yann Ylavic
Following up below users@ discussion on dev@... On Fri, Feb 12, 2016 at 12:47 PM, Yann Ylavic wrote: > On Fri, Feb 12, 2016 at 10:47 AM, Daniel wrote: >> The typical way to block OPTIONS in 2.2 does not need mod_rewrite at all >> IIRC. You just add this in your location/directory: >> >>