DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=34669>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=34669


[EMAIL PROTECTED] changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |REOPENED
         Resolution|INVALID                     |




------- Additional Comments From [EMAIL PROTECTED]  2005-04-28 20:00 -------
OK, I've done more investigation. I believe what's happening is that the 
unprocessed flag in the cookies object is getting set to false before the 
headers are all available. Here's why: I put a breakpoint in my servlet filter 
just before I get the session. I ask for the cookies and I break if cookies 
returns null.

Then I go into the data structure and look at the CoyoteRequest object. The 
Cookies object has unprocessed=false and no cookies, but the headers include a 
cookie header.

I reset unprocessed to true, then I reaccess Cookies and the JSESSIONID cookie 
appears.

More data: I put a breakpoint in the cookie parser and it never failed to find 
the header. So what I'm wondering is if there is a case where parsing might be 
bypassed? For example, it looks like the cookies are normally processed on 
object creation and then if recycle is called. Could the headers sometimes be 
getting set without calling recycle?

The other bug I'm seeing is that sometimes the scheme isn't set on the 
request. request.getScheme returns null (which breaks redirect).

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to