fix 1.3's ap_proxy_date_canon error handling

like 2.0/2.2/trunk

I'm looking for a conceptual +1 out there.

I've barely tested it and need to summarize the diffs
between ap_ and
apr_ functions again.  (e.g., "apr_date_parse_http
supports format XXX
that ap_parseHTTPdate() doesn't support, but
ap_proxy_date_canon()
didn't allow that before anyway so it doesn't
regress...")

-- 
Born in Roswell... married an alien...

On Oct 22, 2007, at 7:20 PM, Jeff Trawick wrote:

> like 2.0/2.2/trunk
>
> I'm looking for a conceptual +1 out there.
>

You got it. Conceptual +1 

On 10/23/07, Jim Jagielski <jimjagunet.com> wrote:
>
> On Oct 22, 2007, at 7:20 PM, Jeff Trawick wrote:
>
> > like 2.0/2.2/trunk
> >
> > I'm looking for a conceptual +1 out there.
> >
>
> You got it. Conceptual +1 

Thanks ;)  Kind of silly I realize, but I wanted to make
sure that if
I spend more time on this then somebody is likely to
read/review
further.

On Oct 23, 2007, at 10:21 AM, Jeff Trawick wrote:

> On 10/23/07, Jim Jagielski <jimjagunet.com> wrote:
>>
>> On Oct 22, 2007, at 7:20 PM, Jeff Trawick wrote:
>>
>>> like 2.0/2.2/trunk
>>>
>>> I'm looking for a conceptual +1 out there.
>>>
>>
>> You got it. Conceptual +1 
>
> Thanks ;)  Kind of silly I realize, but I wanted to
make sure that if
> I spend more time on this then somebody is likely to
read/review
> further.
>

No prob... plus, not only read and review but vote