On 21.01.2010 08:20, wr...@apache.org wrote:
> Author: wrowe
> Date: Thu Jan 21 07:19:41 2010
> New Revision: 901578
>
> URL: http://svn.apache.org/viewvc?rev=901578&view=rev
> Log:
> Correctly align the behavior of headers_in to be consistent with the
> treatment of headers_out, resolving PR 4835
On 1/20/2010 11:01 PM, Paul Querna wrote:
> I think i'll take the 1.4.2 APR tag, and try to use APR-Util 1.3.9
That sounds sensible. I looked at either dropping crypto or backing up
to use the first take (as in the 2.3.4-alpha tarball), but really don't
want to do either hastily, with no feedback
I think i'll take the 1.4.2 APR tag, and try to use APR-Util 1.3.9
On Wed, Jan 20, 2010 at 3:17 PM, William A. Rowe Jr.
wrote:
> On 1/20/2010 4:56 PM, Sander Temme wrote:
>>
>> On Jan 20, 2010, at 9:42 AM, William A. Rowe Jr. wrote:
>>
>>> On 1/20/2010 10:01 AM, Sander Temme wrote:
And
I man seteuid in my Linux box, there are two types of errors:
ERRORS
The seteuid() function shall fail if:
EINVAL The value of the uid argument is invalid and is not supported by
the implementation.
EPERM The process does not have appropriate privileges and uid does
not
to represent when process was started and when it was last used.
Any concerns with this somewhat gratuitous change?
(also changes "Requests handled" to "Accesses")
now:
Pid Active IdleAccessesState
30890 99 0 1479Ready
and after all such tables:
"Active and I
On 1/20/2010 4:56 PM, Sander Temme wrote:
>
> On Jan 20, 2010, at 9:42 AM, William A. Rowe Jr. wrote:
>
>> On 1/20/2010 10:01 AM, Sander Temme wrote:
>>>
>>> And the %lld printf formatter on MacOSX... small, but it does break a test.
>>
>> That's fixed on the branch, or no? About to tag 1.4.2.
>
On Jan 20, 2010, at 9:42 AM, William A. Rowe Jr. wrote:
> On 1/20/2010 10:01 AM, Sander Temme wrote:
>>
>> And the %lld printf formatter on MacOSX... small, but it does break a test.
>
> That's fixed on the branch, or no? About to tag 1.4.2.
I'm about to get on a flight, will test once under
On 20 Jan 2010, at 10:47, bugzi...@apache.org wrote:
> https://issues.apache.org/bugzilla/show_bug.cgi?id=48359
>
> --- Comment #7 from Ruediger Pluem 2010-01-20 03:47:50
> CET ---
> (In reply to comment #6)
>> It's a RFC - if your comment represents a +1, I'm happy to revert and commit
>> a p
During the last hackathon, Paul was kind enough to run the clang/llvm
static analysis on mod_fcgid
(http://zeus.kimaker.com/~chip/fcgid-scan/). That pointed out these
setuid()/seteuid() calls that aren't checked prior to running a child.
The error checking itself is simple enough, but there's an
Just a quick reminder that the httpd & incubating Traffic Server
hackathon happens at the Google Campus in Mountain View CA this
coming Mon and Tues. There's still time to register, just add
yourself to the wiki page at;
http://wiki.apache.org/httpd/HTTPD%2BTS%2BHackathon
and expect the simulc
On Wed, Jan 20, 2010 at 12:41 PM, William A. Rowe Jr.
wrote:
> On 1/20/2010 6:05 AM, Jeff Trawick wrote:
>> Let me know if another day or two would help. (I'll look at a couple
>> of issues myself to see if they have simple/safe solutions.)
>
> Actually, if you can tag this by tomorrow afternoon,
On 1/20/2010 10:01 AM, Sander Temme wrote:
>
> And the %lld printf formatter on MacOSX... small, but it does break a test.
That's fixed on the branch, or no? About to tag 1.4.2.
On 1/20/2010 6:05 AM, Jeff Trawick wrote:
> Let me know if another day or two would help. (I'll look at a couple
> of issues myself to see if they have simple/safe solutions.)
Actually, if you can tag this by tomorrow afternoon, I should be able
to vote on it before the weekend, otherwise I won't
On Jan 19, 2010, at 6:14 PM, William A. Rowe Jr. wrote:
>> For APR, we can use 1.4.1:
>> http://svn.apache.org/repos/asf/apr/apr/tags/1.4.1/
>
> Actually 1.4.1 is going not-released, because of a significant hash/table
> regression. But I'll make life easy, and tag 1.4.2 [essentially 1.4.1 less
Let me know if another day or two would help. (I'll look at a couple
of issues myself to see if they have simple/safe solutions.)
On Tue, 2010-01-19 at 16:54 -0800, Jeff Tharp wrote:
> That does fix this issue, but the browser still gets a 200 instead of a 404.
> I know that's caused some confusion for our operation as well. Think about
> SEO here -- we have a site behind an Apache-based reverse proxy. We want to
> use
On Wed, Jan 20, 2010 at 01:54, Jeff Tharp wrote:
> That does fix this issue, but the browser still gets a 200 instead of a 404.
> I know that's caused some confusion for our operation as well. Think about
> SEO here -- we have a site behind an Apache-based reverse proxy. We want to
> use Pro
17 matches
Mail list logo