Re: [Webware-devel] Request.isSecure hard coded to return 0 and SERVER_PROTOCOL doesn't show HTTPS

2001-09-13 Thread Geoff Talvola
At 03:15 PM 9/13/01 -0400, Jeff Johnson wrote: >In Request.py: > > def isSecure(self): > ''' Returns true if request was made using a secure >channel, such as HTTPS. This currently always returns false, since >secure channels are not yet supported. ''' > ret

[Webware-devel] Request.isSecure hard coded to return 0 and SERVER_PROTOCOL doesn't show HTTPS

2001-09-13 Thread Jeff Johnson
In Request.py: def isSecure(self): ''' Returns true if request was made using a secure channel, such as HTTPS. This currently always returns false, since secure channels are not yet supported. ''' return 0 Is this still true? I thought I was using HTTPS

RE: [Webware-devel] Bad cookies hang Webkit

2001-09-13 Thread Geoff Talvola
At 11:10 AM 9/13/01 -0400, Jeff Johnson wrote: >Ok, here's the diffs. The only other change than the two exception >handlers is a print "." that somehow fixes the FreeBSD restart problem. I checked in your diffs to CVS with minor changes (comments and added "import sys" to one module). -- -

RE: [Webware-devel] Bad cookies hang Webkit

2001-09-13 Thread Jeff Johnson
Ok, here's the diffs. The only other change than the two exception handlers is a print "." that somehow fixes the FreeBSD restart problem. Thanks, Jeff > At 10:04 AM 9/13/01 -0400, Jeff Johnson wrote: > >I had forgotten about this until last night when someone > with (I assume) > >corrupted

RE: [Webware-devel] Bad cookies hang Webkit

2001-09-13 Thread Geoff Talvola
At 10:04 AM 9/13/01 -0400, Jeff Johnson wrote: >I had forgotten about this until last night when someone with (I assume) >corrupted cookies hung WebKit again by killing off all the threads. Can >we have two exception handlers? One to catch corrupted cookies and >another to prevent unexpected exc

RE: [Webware-devel] Bad cookies hang Webkit

2001-09-13 Thread Jeff Johnson
I had forgotten about this until last night when someone with (I assume) corrupted cookies hung WebKit again by killing off all the threads. Can we have two exception handlers? One to catch corrupted cookies and another to prevent unexpected exceptions from killing off all the threads? I've tes