Mailing-List: contact modperl-help@perl.apache.org; run by ezmlm
Precedence: bulk
Received-SPF: pass (hermes.apache.org: local policy)
Message-ID: <4193EE48.1070702@rayman.com>
Date: Thu, 11 Nov 2004 14:57:12 -0800
From: ___cliff rayman___ <cliff@rayman.com>
User-Agent: Mozilla/5.0 (Windows; U; Win98; en-US;
 rv:1.4) Gecko/20030624 Netscape/7.1 (ax)
MIME-Version: 1.0
To: modperl@perl.apache.org
Subject: Re: Apache::Cookie
References: <4190EF57.4020502@m-cam.com>
 <87zn1ol5to.fsf@gemini.sunstarsys.com> <4193B6D0.3090100@modperlcookbook.org>
 <4193E7AA.6020607@m-cam.com>
In-Reply-To: <4193E7AA.6020607@m-cam.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Arshavir Grigorian wrote:

> Geoffrey Young wrote:
>
>>> libapreq2 is currently using $r->headers_out instead
>>> of $r->err_headers_out, which is why you're not seeing the
>>> cookie on your redirect response.  I think the consensus
>>> is that this is a bug in libapreq2-2.04, but I haven't seen
>>> any other apreq committers weigh in on the subject, so
>>> I'm not sure.
>>>   
>>
>>
>> libapreq1 uses error_headers_out, so I think it's proper to follow 
>> that well
>> established tradition, fwiw.
>>
> Thanks for the feedback. I guess I am wondering who I would need to 
> talk to in order to get this fixed.
>
> Just to understand, why does it need to use the err_headers_out 
> instead of headers_out? There does not seem to be any errors. Am I 
> misinterpreting the function name or is it a misnomer?

I have run into this in the past, and just rediscovered it again last 
week.  A redirect response is either generally 301 or 302.  Since it is 
not a 200 level response, this could be the reason. that  error headers 
out needs to be set, instead of just the regular headers

-- 
_____cliff_rayman_____cliff_@_rayman_._com_____


-- 
Report problems: http://perl.apache.org/bugs/
Mail list info: http://perl.apache.org/maillist/modperl.html
List etiquette: http://perl.apache.org/maillist/email-etiquette.html