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=32814>.
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=32814

           Summary: Tomcat 5.0.27 refuses connection if secure cookie in
                    session?
           Product: Tomcat 5
           Version: 5.0.27
          Platform: Macintosh
        OS/Version: Mac OS X 10.0
            Status: NEW
          Severity: critical
          Priority: P2
         Component: Unknown
        AssignedTo: tomcat-dev@jakarta.apache.org
        ReportedBy: [EMAIL PROTECTED]


Seasons Greetings!

I start up Safari and can get to the root page of Tomcat through SSL, which I 
have enabled in the
server.xml.

I have a local Apache module which allows a secure login and maintains session 
state by puting a 
cookie in the browser.  It is a secure cookie that is digitally signed.

When my browser has that cookie, I can no longer connect to Tomcat through SSL. 
 If I manage the 
cookies and remove that one cookie, I can once again connect to Tomcat through 
SSL.  Throughout 
this, I can connect to Tomcat when I don't use SSL.

I can't find any debugging or logging information about what is happening.  
It's like the browser no 
longer reaches Tomcat.

Safari says The error was: “bad server response” (NSURLErrorDomain:-1011).
Also cannot connect with Netscape 7.02.   It simply says the document contains 
no data.

I set the debugging level to 4 everywhere in server.xml and enabled the request 
dumper, but I still 
cannot see any sign that the request reaches Tomcat.

Thanks for your help.
==Leonard

-- 
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