Aaron Bannert wrote:
On Mar 29, 2005, at 8:47 AM, Jim Jagielski wrote:
Since we're extending core_dir_config, we should document the
change in core_dir_config
Should I elaborate more in my core_dir_config from what I already have?
I mean in ap_mmn.h
--
If there's no objection, shall I just go ahead and commit this?
-aaron
On Mar 24, 2005, at 4:38 PM, Aaron Bannert wrote:
I've attached a patch against the trunk of Apache 1.3 that backports
support for the AllowEncodedSlashes directive. It should behave
identically to the way it works in 2.0. By
Since we're extending core_dir_config, we should document the
change in core_dir_config
Aaron Bannert wrote:
If there's no objection, shall I just go ahead and commit this?
-aaron
On Mar 24, 2005, at 4:38 PM, Aaron Bannert wrote:
I've attached a patch against the trunk of Apache 1.3
At 10:47 AM 3/29/2005, Jim Jagielski wrote:
Since we're extending core_dir_config, we should document the
change in core_dir_config
Since the bit breaks binary compatibility, I'll toss my -1 into
the ring. It's non-technical though, so not a veto.
I wish we had pool datum, which would
William A. Rowe, Jr. wrote:
At 10:47 AM 3/29/2005, Jim Jagielski wrote:
Since we're extending core_dir_config, we should document the
change in core_dir_config
Since the bit breaks binary compatibility, I'll toss my -1 into
the ring. It's non-technical though, so not a veto.
I wish
At 04:56 PM 3/29/2005, Jim Jagielski wrote:
William A. Rowe, Jr. wrote:
At 10:47 AM 3/29/2005, Jim Jagielski wrote:
Since we're extending core_dir_config, we should document the
change in core_dir_config
Since the bit breaks binary compatibility, I'll toss my -1 into
the ring. It's
On Mar 29, 2005, at 8:47 AM, Jim Jagielski wrote:
Since we're extending core_dir_config, we should document the
change in core_dir_config
Should I elaborate more in my core_dir_config from what I already have?
Index: src/include/http_core.h
I've attached a patch against the trunk of Apache 1.3 that backports
support for the AllowEncodedSlashes directive. It should behave
identically to the way it works in 2.0. By default Apache will disallow
any request that includes a %-encoded slash ('/') character (which
is '%2F'), but by enabling
