I have a request to all posters to the AOLserver discussion group:
please take the time to use reasonably good subject lines in your
messages. The subject line above doesn't tell me anything about the
content, but it could. I better line might have been:
AS 3.4 and PG 7.2.1 - occasional crash
Title: Message
If you mean
that all the ns_sock* commands are to be documented under one ns_sock.n man
page, I have to disagree. It breaks the unix standard of one command per man
page. I wouldn't know to look in ns_sock.n for ns_sockopen; the user should not
need to know what file a comma
Title: Message
Not
completely true.
The Tcl
commands are documented on separate man pages -- the 'for' and 'foreach' Tcl
commands are on their own separate pages, and the See Also leads you to the
other commands.
The Tcl C
API is a different story -- in this case, the multiple C API fun
> I find, for example, that the traditional AOLserver documentation
including all
> variants of ns_return on a single page helps me to better understand
the range
> of responses available.
After reviewing this, I now see what you're saying. The problem is that
the second part of some command name
Title: Message
I Agree.
We'll do the 3.5 docs first as-is. I think at some point
we should bite the bullet and rename commands like
ns_returnadminnotice
to
be
ns_return adminnotice
and
maintain that consistency throughout the server and modules. Backward compatibility
would be
Title: Message
What was
the new chat time on Thursdays? Last stated was 3pm Eastern, but then you asked
for any takers at 2pm Eastern. I abstained, and no one else spoke up, so I'm
assuming it was finally changed to 3pm Eastern.
I intend to
hang out in the chat room all day from now on.
Hi Daniël,
Yes, this would be useful, maybe as a standard ns_* style command,
something like an ns_bind_vars.
Right now the focus is on setting up a core AOLserver team, getting
AOLserver 3.5.0 fully documented, getting the current modules cleaned
up/documented, getting AOLserver 4.0 released, an
Title: Message
If anyone
from the OpenACS community would like to nominate themselves, please send your
brief paragraph or two to Nathan.
/s.
-Original Message-From: AOLserver
Discussion [mailto:[EMAIL PROTECTED]] On Behalf Of Simon
MillwardSent: Tuesday, November 05, 2
Good question. In about six months I expect AOLserver and all of the
modules to be fully tested, documented and clean. At that point, it will
be hard to argue with using AOLserver for any kind of IT project from a
technical or maintenance standpoint. It is the other arguments we will
have to overc
-Original Message-
From: AOLserver Discussion [mailto:AOLSERVER@;LISTSERV.AOL.COM] On Behalf
Of [EMAIL PROTECTED]
Sent: Friday, November 08, 2002 12:29 AM
To: [EMAIL PROTECTED]
Subject: [AOLSERVER] Other languages (was: Project Update)
> I think Tcl (or, rather, "single language support")
Exactly. Even though they work for AOL, they are still a part of the
AOLserver community and should have a vote. I wish I could have put it
this clearly.
/s.
-Original Message-
From: AOLserver Discussion [mailto:AOLSERVER@;LISTSERV.AOL.COM] On Behalf
Of Jeff Hobbs
Sent: Friday, November
Title: Message
It appears there are a
few man pages showing up in the 4.x (HEAD) branch that should have been
committed to the aolserver_35_bp branch.
To avoid any confusion,
please send me the man pages you've signed up for when you've finished them and
I'll commit them to the right branc
There are three ways to invoke Emacs nroff mode while working on the
AOLserver man page documentation:
1. Tell Emacs that files ending with the .n suffix are to be edited in
nroff-mode by placing this text in your .emacs file:
; Edit .n files in nroff mode. Files ending with a number
; as a suff
On Monday, January 6, 2003, at 04:30 PM, Jeff Hobbs wrote:
In any case, I did want to mention that since 8.2 Tcl has had stacked
channels in the core. Extensions like Trf, memchan and TLS use this
to do compression and/or encryption on channels transparent to the
user.
gzip gets a bit more comp
On Monday, January 6, 2003, at 11:10 PM, Jeffrey Hobbs wrote:
That's a good question ... I've never actually done performance
analysis on the stacked channel stuff, but it is fairly efficient.
It just passes buffers from one stack to the next as they are
consumed. Special purpose filters may do
AOLserver 4.0 hasn't been released -- you can get the code by checking
out the "aolserver" module from AOLserver's CVS SourceForge area.
/s.
On Wednesday, January 8, 2003, at 03:18 PM, Niels Hallenberg wrote:
Hi There,
On Wed, 8 Jan 2003 14:38:15 EST, Jim Davidson <[EMAIL PROTECTED]>
wrote:
Yeah, it's a bad HTTP request. 400 means that the server determined a
syntax error in the request. It looks like some automated program is
performing conns to your server but not sending any HTTP info over,
since the "GET" or other HTTP method isn't being stored in the log.
Something may be connect
Hi Keith,
Just append all the CA cert files in the chain into one file, then use
the ServerCAFile param to point to it. These CA cert files should be in
PEM format. We're using that here for our DoD CA chain and it works
great.
/s.
On Thursday, January 16, 2003, at 12:07 PM, Keith Paskett wrote
After looking through the 3.4.2 source code, the answer is no. TRACE is
not a supported HTTP method in AOLserver. I used cscope to find all
occurences of TRACE and found none. Also checked the Tcl module that
come with the server.
It might be wise to register a proc to log that a TRACE request was
On Wednesday, January 22, 2003, at 03:48 PM, Andrew Piskorski wrote:
Incidentally, Apache/1.3.26, the version shipped with Debian 3.0, DOES
implement TRACE.
On Wed, Jan 22, 2003 at 01:04:36PM -0800, Jade Rubick wrote:
Does Aolserver implement the TRACE command?
http://www.extremetech.com/articl
wrote:
Scott Goodwin wrote:
have the source code.
We use AOLserver for EMIS, which is not vulnerable. I've added extra
checking to the EMIS request processor 5 minutes ago to log any
attempts
to use HTTP methods that we don't accept so we can identify attempts
to
use TRACE. Here'
003 04:53 pm, Jerry Asher wrote:
Scott Goodwin wrote:
have the source code.
We use AOLserver for EMIS, which is not vulnerable. I've added extra
checking to the EMIS request processor 5 minutes ago to log any attempts
to use HTTP methods that we don't accept so we can identify attempts to
us
I think a registered filter put in before any other filter would be
better, unless you have a specific error page you want to show that's
in OpenACS. My code is returning our error page; I wouldn't want to
rely on a more complex module to perform this function for me. A bug in
your rewrite code cou
Adobe's Acrobat Viewer supports byte range serving when installed as a plug-in for Netscape Navigator, or as an ActiveX control for Microsoft's Internet Explorer. It'll pull down a page at a time as you move through the document.
/s.
On Thursday, January 23, 2003, at 06:47 PM, Jim Davidson wrot
Several people have contacted me about the CVS copy of nsopenssl.
The CVS nsopenssl code will not currently compile with AOLserver 4.x,
so please don't try to compile it.
I had planned to have this upgrade finished by the 1st of Jan. My
apologies for not having it finished. The changes I am makin
Hi all,
can those of you with Cold Fusion experience please respond to me
directly with your opinions on Cold Fusion vs Tcl in AOLserver?
I need to make a case for moving a heavy Cold Fusion developer group to
Tcl in AOLserver. Specifically I need to convince this group that the
pain of the switc
Pull the CVS copy of nspostgres -- I believe that one works with
AOLserver 4.x, but hasn't been packaged for a release yet.
/s.
On Monday, February 10, 2003, at 09:22 AM, Wes James wrote:
I tried to compile nspostgres 3.5 and I get compile errors with aols4.
I
then try it again with aols351 t
John Caruso pointed this out a couple of weeks ago. Read below:
From: John Caruso <[EMAIL PROTECTED]>
Date: Fri Feb 21, 2003 5:57:14 PM US/Central
To: [EMAIL PROTECTED]
Subject: Test for THREADS in thread.c (in nsopenssl 2.1)
I'm in the process of (re)building nsopenssl 2.1 using openssl 0.9.7a,
Do you have session caching turned on?
/s.
On Monday, March 10, 2003, at 11:00 PM, William Scott Jordan wrote:
I'm running AOLServer 3.4 with OpenSSL 0.9.6 and nsopenssl 2.2b4 on
Redhat
7.0 and I'm getting this error quite a bit:
Error: nsopenssl: EOF during SSL handshake
I have no idea what's
Turn it on, always, always, always have session caching on, or SSL to
certain MSIE browser versions will fail in the way you're seeing. I've
just updated the nsopenssl config examples at my site to reflect this.
nsopenssl 3.0 will have session caching turned on by default, so that
if you want it tu
om
ns_param SeedBytes 1024
Thanks,
-Oscar
On Mon, Mar 10, 2003 at 11:42:36PM -0600, Scott Goodwin wrote:
Turn it on, always, always, always have session caching on, or SSL to
certain MSIE browser versions will fail in the way you're seeing. I've
just updated t
Note that you will see some EOFs in the log files that are normal and
aren't due to failures. I see them all the time because we're using
client certs -- MSIE makes a connection, realizes the server wants a
client cert, cuts the conn (EOF), asks the user which client cert they
want to use, then mak
Find out what browser types and versions you expect your users to use
and go see what CA certs are preloaded into them. That's the list of
CAs you should choose from. Getting a server cert from anyone else, or
generating your own, will cause your user's browsers to popup the
"invalid site" warning.
On 3/17/03 11:17 AM, "Janine Sisk" <[EMAIL PROTECTED]> wrote:
> Hear, hear! :)
>
> I keep hearing about the studliness of Emacs and it's not that I don't
> believe it - but my fingers know Vi extremely well, after using it for
> nigh on 15 years (ok, that's a scary thought in itself!) and it slows
I believe you limit the request line like so:
ns_section "ns/server/${servername}"
ns_param maxline 10240
It defaults to 8192 in AOLserver 3.5.1.
The config file should be placed in the top level of your AOLserver
installation area, and should be called nsd.tcl. For a new
installation,
Send me the patch and tell me what the previous version was (i.e. is it
the current CVS copy that doesn't do what you expect?).
/s.
On Monday, March 24, 2003, at 02:35 PM, Daniel P. Stasinski wrote:
In the newest nsxml module, is there a way to produce indented
output rather than all on one line
Hi Matthew,
Sounds like a memory leak in nscgi. Can you send me the perl script and
your nsd.tcl file? I'll see if I can duplicate the problem, track it
down and fix it.
thanks,
/s.
On Friday, March 28, 2003, at 04:57 PM, Matthew Krenzer wrote:
I know this subject was addressed a while ago but
Go get nsopenssl 2.1 and look at the https.tcl file in that
distrubution: I've added ns_httpspost to it, and it even does multipart
forms!
Take my changes and apply them to the http.tcl file that comes with
AOLserver and you'll have what you need.
Send me the resulting http.tcl file and I'll commit
Of course that was easy. What, did you think this was Apache?!?
/s.
On Thursday, April 3, 2003, at 10:32 AM, Wolfgang Winkler wrote:
Hi!
I just changed the line from
set http [ns_httpsopen POST $url $rqset $timeout $querystring]
to
set http [ns_httpopen POST $url $rqset $timeout $querystring
Matthew,
I've tracked down the CGI memory leak; it should be fixed in about an
hour in both the 3.5 branch and 4.x.
/s.
On Friday, March 28, 2003, at 04:57 PM, Matthew Krenzer wrote:
I know this subject was addressed a while ago but I'm curious to know
if
there has been any resolution to this.
W
Problem Report on nscgi Memory Leak:
!!! THIS IS A MAJOR BUG FOR ANYONE RUNNING CGI SCRIPTS IN AOLSERVER 3.x
!!!
This bug exists in released versions of AOLserver 3.x inclusive of
AOLserver 3.5.1 all the way back to AOLserver 3.0. Any past or current
reports of AOLserver 3.x growing in size over t
This is a very useful feature that would be very helpful for new users
especially. I think it's so good, I would prefer to see it integrated
such that you trigger it with a command line flag to nsd at start time.
Many of you use other tools to perform watchdog activities, which is
great. But others
Yes, I am able and willing to do this. I was also taking over as
moderator for the core team meetings starting next week, but it appears
you and/or Mark now have the time to devote to that role and you have a
set of agenda items so I'll step back from that role.
/s.
On Friday, August 1, 2003, at 0
Hi all,
I'm identifying maintainers for the AOLserver modules, and I'm going to
begin with the database modules. Here is a list of the database modules
I know of and who the primary maintainer is.
Please email me directly (*do not reply to the list*) to confirm what I
have here, make corrections,
As per the conversation during the AOLserver chat today, I've posted
the webdav.tcl module to my site's front page: http://scottg.net.
/s.
--
AOLserver - http://www.aolserver.com/
To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]> with the
body of "SIGNOFF AOLSERVER" in
Hi Jeremy,
you should find most of what you need at http://www.aolserver.com. Look
along the left edge for links to documentation etc. You'll specifically
want to look at ADPs (AOLserver Dynamic Pages), which you can find here:
http://aolserver.com/docs/devel/tcl/adp-overview.html
/s.
On Monday,
Peer verify means the server will request the client to send a client
SSL cert. You will rarely ever use this option, and if you're not sure
whether you need it, then you definitely don't. Most clients (i.e.
users with browsers) don't have their own personal certs. You might use
it to gain access t
Am I missing something here? Is there some reason I might ever want
to have this message in my server log at all?
Probably not. Cleaning up log messages is on my todo list but not a
high priority at the moment.
/s.
On Wednesday, Sep 24, 2003, at 11:45 US/Eastern, Andrew Piskorski wrote:
I recent
Scott, would you be so kind to enlighten me?
Certainly. Important parts of my test config are at the bottom of this
message. Here's how it works:
At start time, nsopenssl reads the config sections for SSL contexts and
SSL drivers. Each SSL context and each SSL driver has a unique name
within that v
ns_conn close doesn't clean up the SSL part of the connection so it's
possible these errors are generated after ns_conn close, which might
leave the channel in existence but in an unknown state. reading/writing
to the channel after ns_conn close would mean bytes reach the channel
but the channel do
Thanks for the feedback. I've decided to split nsopenssl into two
modules. The nsopenssl module will now be entirely focused on
AOLserver's comm-driven connections. The nshttps module will focus on
creating and using SSL connections using a Tcl API.
I've made the decision to split this effort in tw
On Tuesday, September 30, 2003, at 04:11 AM, Andrew Piskorski wrote:
I realize this must be awfully late in the coding to bring up, but:
Would it greatly simplify or speed up things to release a first
version of nsopenssl which works with AOLserver 4.0, but does NOT
support virtual servers in any
If you have a sourceforge account, do this:
cvs -z3 -d:ext:[EMAIL PROTECTED]:/cvsroot/aolserver
co -r aolserver_v35_bp aolserver
but change 'scottg' to your username.
Otherwise, do this:
cvs -d:pserver:[EMAIL PROTECTED]:/cvsroot/aolserver login
cvs -z3 -d:pserver:[EMAIL PROTECTED]:/cvsroot/aolse
The text beginning at "Content-Dis..." should be on the next line by
itself. If the browser hasn't changed, but the server has, then there
is something on the server side that's at fault. How are you processing
the incoming files? I.e. show us the code that touches file uploads in
your ADP or Tcl l
e should get it committed to sf cvs so people can start updating the
code in one place.
Scott Goodwin wrote on 8/21/03, 3:38 PM:
> As per the conversation during the AOLserver chat today, I've posted
> the webdav.tcl module to my site's front page: http://scottg.net.
>
> /s.
--
Sorry, that should read http://scottg.net/download/webdav.tcl
/s.
On Thursday, October 9, 2003, at 09:18 PM, Scott Goodwin wrote:
It's in SourceForge CVS, but you can still get the copy from
http://scottg.net/downloads/webdav.tcl
/s.
--
AOLserver - http://www.aolserver.com/
To R
This kind of problem is notoriously difficult to reproduce and will
require an extensive code review on my part to identify where the
problem may be occurring. It is possible that I am doing/not doing
something in the code that is contributing to this. I'll see if I can
track down the problem, but
symptoms; if you went to a secure page, and sat there for a
while, then
went to another page, you would get a "page not found" error. What I
had to
do was to change the keepalivetimeout parameter to 0 in the nsd.tcl
file.
This disables that timeout. I believe it may have been Scott Goodwi
Can the person from Greenpeace who directly emailed me yesterday about
nsopenssl please resend your message. I did receive it but I simply
cannot find it in my inbox, deleted items or any other folder. Very
strange.
thanks,
/s.
--
AOLserver - http://www.aolserver.com/
To Remove yourself from this
nsopenssl 3.0 beta 10 is available on http://scottg.net. Kick the tires.
/s.
--
AOLserver - http://www.aolserver.com/
To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]> with the
body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: field of
your
Forgot to mention that you'll have to get around the fact that
ServerPort is no longer a valid name in the config -- OpenACS will have
an issue with that.
Since you can now have multiple drivers per virtual server, and drivers
for each virtual server, you'll have to figure out a way for OpenACS to
No, you're not being paranoid. Are you using nscgi and running CGI
scripts? If so, then you're running into this problem (from the
ChangeLog):
2003-04-04 Scott S. Goodwin <[EMAIL PROTECTED]>
* nscgi/nscgi.c: (bug) Ns_DStringInit called in CgiExec was
destroying the
linked list used to m
ed we fall.
- Original Message -
From: "Scott Goodwin" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, January 08, 2004 15:37
Subject: Re: [AOLSERVER] nsd and memory leaks
No, you're not being paranoid. Are you using nscgi and running CGI
scripts? If s
Beta 11 is now on my site (http://scottg.net). A fix for problems with
downloading/uploading files that are larger than your average web page.
/s.
--
AOLserver - http://www.aolserver.com/
To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]> with the
body of "SIGNOFF AOLSE
The problem doesn't exist in the current CVS HEAD copy of AOLserver.
/s.
On Jan 13, 2004, at 4:53 PM, C. R. Oldham wrote:
Greetings,
Has anyone been able to look into the shutdown problem with the 4.0 GM
release of AOLserver?
--
C. R. Oldham
Director of Technology
NCA CASI
--
AOLserver - http:/
compiled in. If you run into this issue, add this to your CFLAGS +=
line:
-I/usr/kerberos/include
This fix will be in the next release. Kick the tires and report any
flats.
/s.
On Jan 19, 2004, at 3:00 PM, Scott Goodwin wrote:
Attached is beta 12. Please test to see if your images issue is fixed.
I
Why are you using the same file for both your Certificates and your
list of CA Certificates to validate incoming certificates with? When a
client passes you their certificate, nsopenssl uses the CA certificates
in the CAFile to validate that client certificate. Based on what I see
below, you're usi
Use the CAFile param -- ignore the CADir param. Simply take all the CA
certificates you have that you want to use to validate peer
certificates with and concatenate them together into one file. The CA
certificates have to be in PEM format.
You only use them when you have PeerVerify set and you actu
If ns_httpsget generated the error, then $response never got set. I
suspect your connection is failing in the SSL handshake portion. Check
obvious things like are you connecting to the correct IP and Port, is
that port running SSL, etc. You didn't specify what version of
nsopenssl you're running.
/
nsoracle 2.7 is now available on SourceForge in the file downloads
area. Please look at the ChangeLog for more info. Much thanks to Jeremy
Collins, who did all the work.
/s.
--
AOLserver - http://www.aolserver.com/
To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]> with
On Feb 10, 2004, at 10:36 AM, [EMAIL PROTECTED] wrote:
Also, Jeff Davis of the OpenACS crew has been de facto maintainer of
the
driver - do you plan to talk to him before moving forward?
There haven't been any defacto maintainers since Jeremy and Jeff
stepped up to be co-maintainers of nsoracle qu
Jeremy, Jeff,
would it be possible to create a regression test suite that exercises
the functionality? It could include a simple set of SQL files to load
into the db and then run the tests against.
/s.
On Feb 10, 2004, at 1:02 PM, [EMAIL PROTECTED] wrote:
On Feb 10, 2004, at 9:36 AM, [EMAIL PROT
Sorry I haven't responded -- very busy on a work project.
Essentially what's happening is the core driver keeps calling
nsopenssl's read function even when there's nothing ready to be read
yet. The infinite loop isn't really infinite because the connection is
still alive, but the client hasn't sen
When I worked at DoD I placed their root CA cert first, then the
intermediate CAs after, all concatenated into one file that I then
pointed to with ServerCAFile -- this worked fine. Ensure you don't have
any corruption of the file, as might happen if it has DOS-style line
endings.
/s.
On Feb 27, 2
Occurs when client doesn't send data before driver's recvwait value has
expired. Probably innocuous, specifically if keepalive is set.
/s.
On Feb 26, 2004, at 10:39 PM, Dossy wrote:
Is there any reason why seeing something like this in my server log
should cause me to be suspicious:
[26/Feb/2004:
I've fixed the problem and will have beta 14 online once I'm able to
connect to sourceforge to commit the changes. AOLserver core code is
fine. Problem was I needed to wait on the socket if the socket was
still valid but had no bytes ready.
/s.
On Feb 27, 2004, at 1:11 PM, Scott Goo
I'm unable to connect to SF via CVS to checkin or checkout code. Can
someone try to get something from AOLserver CVS area using their login
mode (i.e. don't use anonymous pserver access) and post here if they
can get to it?
thanks,
/s.
--
AOLserver - http://www.aolserver.com/
To Remove yourself f
Problem solved; changed my env set up last week and CVS_RSH stopped
being exported.
thanks,
/s.
On Feb 29, 2004, at 7:22 AM, Dossy wrote:
On 2004.02.28, Scott Goodwin <[EMAIL PROTECTED]> wrote:
I'm unable to connect to SF via CVS to checkin or checkout code. Can
someone try to ge
I've committed and tagged v3_0beta17 and it's up at scottg.net. This
should resolve problems where slow or non-responsive clients cause
nsopenssl to soak up all your CPU. Report any odd behavior to me; in
particular, look for "SSL_ERROR_*" messages in your log files. If you
see any, send me copies
Mac OS X also comes with uuidgen, which probably means the other BSDs
do as well. The code seems straightforward enough to turn it into a
loadable module.
I'm using a simple random sequence of characters as a session id for
visitors:
set chars
abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXY
Right now you have two choices that I'm aware of: run AOLserver, or
replicate whatever part of its Tcl API you need to test with. For
example, I have several access control procs that work with IP
addresses, usernames and so on. I want regression tests on these to be
run after any changes to the se
Not sure this still applies. This code section has changed
significantly in the main branch and maxpost has been replaced by
maxinput, or so it appears. Might still want to file it a as a bug on
SF as Zoran suggested (with the right AOLserver version it affects) so
we do have a record of it.
/s.
O
Here's the pertinent text from Microsoft:
http://www.microsoft.com/technet/security/bulletin/MS04-004.mspx
Why am I getting errors when attempting to access certain SSL protected
Web Sites?
After installing the Internet Explorer 6.0 SP1 version of this update,
there may be intermittent failures o
andle. I was wondering if there is an http
status code so that the browser would resend the request. Or I could
display an error page that suggest the user update their browser with
831167.
Any ideas on how to handle for external users would be welcome.
Thanks,
Ron Emerick
On Tue, 13 Apr 2004 09:3
Surfer hits page, surfer fills in form info, keepalive idles at 30
seconds, IE believes the session is still there, surfer hits submit,
invalid ssl session, blank page, surfer needs to refresh to see page,
all post info lost.
Yes, this is the behavior IE exhibits with SSL when keepalive is used.
Wh
On Apr 13, 2004, at 2:19 PM, Tomasz Kosiak wrote:
I would certainly opt for having this. But as far as I remember from
disscussion with Piotr Szuca that may be difficult to add to AOLserver
due to current keepalive implementation.
It would probably be difficult to implement for nsopenssl and AOLse
Gustaf,
MSIE versions are riddled with problems. Ensure SSL session caching is
turned on. Looking at the sources, keepalivetimeout is the correct
parameter for AOLserver 4.x -- setting this to 0 disables keepalive
entirely.
Also, MSIE 6.x has intermittent POST problems with the behavior you
mentio
Looks like problem between RH 7.3 and OpenSSL 0.9.7d. Ensure that your
LD_LIBRARY_PATH is set appropriately to point to our compiled version
of OpenSSL libs before starting AOLserver; you might be picking up the
system's SSL libs. If that doesn't work, follow the same build
procedure using earlier
Turn on the Trace param for nsopenssl and look in the logs. I'll bet
the handshake is still failing, but because of something else. Also,
send me (directly) the relevant portion of your nsd.tcl file so I can
review your settings (remove any sensitive info).
/s.
On Apr 22, 2004, at 10:23 PM, Willia
Thanks. Will attempt to recreate next week. I'm currently on vacation
in Florida :)
/s.
On May 10, 2004, at 11:53 PM, Torben Brosten wrote:
Scott Goodwin,
FYI,
Here is another 'assertion "md_c[1] == md_count[1]" failed:' with
similar
conditions that caused server
BTW, I may be pulling down OSSWEB and stealing some code from it...do
you mind?
thanks,
/s.
On Apr 30, 2004, at 10:26 AM, Vlad Seryakov wrote:
Hi,
This is AOLserver module that implements database driver for BerkeleyDB
from www.sleepycat.com
Download
http://www.crystalballinc.com/vlad/software/
--
Torben,
excellent information -- duplicating the problem is 90% of the battle
and the info you've given here may be enough for me to do so.
thanks,
/s.
On May 2, 2004, at 12:50 AM, Torben Brosten wrote:
Scott,
Not sure if you solved this. I came across similar error conditions,
apparently
the resul
It's not a threading issue. AOLserver 4.x opens the listen sockets for
all comm modules including nsopenssl, and the error message is coming
from the DriverThread function in nsd/driver.c when it attempts to
start listening on the port. The reason it says "nsopenssl" is, well,
because that's the na
cs at http://www.scottg.net/webtools/aolserver/modules/nsopenssl
?
/s.
On Jun 3, 2004, at 3:41 PM, Dossy wrote:
Sadly, I do very little with SSL and nsopenssl -- perhaps Scott Goodwin
can say something about this, if he's not too busy?
-- Dossy
On 2004.06.03, Scott Laplante <[EMAIL PROTECTED]> wrot
Hi Mike,
SSL contexts are needed for each client and each server. Multiple
clients can share the same client SSL context, and multiple servers can
share the same server SSL context, but a client cannot share a server's
SSL context and vice versa. See the notes in the nsopenssl distribution
for deta
This is debugging code from a prior beta. Just grab the latest CVS HEAD
for nsopenssl -- latest tag should be v3_0beta21.
/s.
On Jun 30, 2004, at 12:33 PM, Nathaniel Haggard wrote:
The webserver runs for about 6 minutes and then crashes.
The log file is full of this:
[30/Jun/2004:09:24:56][29446.51
My apologies for not being more reponsive; I've been very busy at NASA
these past six months. I'm getting ready to use nsopenssl for the sites
we're building here so I'll be fixing any problems you're seeing in the
next few weeks. I suspect I'm not seeing many of the errors when my
tests are being
2004, at 5:40 PM, Cathy Sarisky wrote:
On Tue, 10 Aug 2004, Scott Goodwin wrote:
purchased two low-end intel boxes to set up a test network and run
load
tests across ethernet; just waiting for two 200GB drives to arrive so
I...
LOL. I like your definition of low-end. Should you find yourself
with
Sisk wrote:
No problem, Scott, glad to hear you're still at it. I hope I didn't
sound like I was complaining; I was just wanting to figure out who, if
anyone, was maintaining the module.
If I can help you sort this out, just let me know.
janine
On Aug 10, 2004, at 5:28 PM, Scott Goodwin
I think that there should be an "else" aftr the SSL_write function and
raise an error if the write wasn't successful ... ?
Actually, once the SSL_read or write has been performed and the total
number of bytes is adjusted, control passes to the switch statement
after it to handle any errors (unless
1 - 100 of 239 matches
Mail list logo
