Re: [AOLSERVER] nsopenssl on NetBSD
Thanks! I thought I was going insane. I will try it at home tonight. Ian A. Harding Programmer/Analyst II Tacoma-Pierce County Health Department (253) 798-3549 mailto: [EMAIL PROTECTED] >>> [EMAIL PROTECTED] 12/11/01 11:57AM >>> I don't think it's an OS problem, I think it was an SSL looping problem. It's fixed in my latest alpha, but I'm going to be extremely busy between now and the 21st on a project here at work, so I won't be doing an official release until after that. The alpha copy is attached; it's essentially production-ready (I'm sending a copy directly to you as the listserv will strip the attachment -- if anyone else wants this copy, let me know). Test with this and tell me if it fixes the problem you're experiencing. /s. > Is anyone else using nsopenssl on NetBSD? I have a wierd problem that I think is OS specific. The client receives the first 16K of data, and nothing more. Usually. Sometimes repeatedly hitting Reload will result in the whole page coming over. > > It happens with nsopenssl 1.0 and 2.0 > It happens with database served pages (nspostgres) and static text files > It happens on the LAN and across the internet. > It happens on the local machine. > It happens with aolserver 3.4 and 3.4.2 > It happens with Internet Exploiter 5.5 and Netscape (unknown version, it's at home) > It happens on Windows clients and NetBSD clients and Linux clients. > > NetBSD is 1.5.2 on i386. > > I thought nsopenssl was closing the connection too soon but it appears not to be. > > I did some squirrely things when compiling openssl to get it to work, for example compiling it with -threads -D_REENTRANT. NetBSD does not support threads natively and I didn't tell openssl anything else about threads, so I don't know what this did, but it did let me get nsopenssl up and seeming to work. nsopenssl was compiled like aolserver, with PTL (Portable Thread Library) . > > Thanks in advance for any ideas... > > > > > Ian A. Harding > Programmer/Analyst II > Tacoma-Pierce County Health Department > (253) 798-3549 > mailto: [EMAIL PROTECTED] > > > >
Re: [AOLSERVER] nsopenssl on NetBSD
I don't think it's an OS problem, I think it was an SSL looping problem. It's fixed in my latest alpha, but I'm going to be extremely busy between now and the 21st on a project here at work, so I won't be doing an official release until after that. The alpha copy is attached; it's essentially production-ready (I'm sending a copy directly to you as the listserv will strip the attachment -- if anyone else wants this copy, let me know). Test with this and tell me if it fixes the problem you're experiencing. /s. > Is anyone else using nsopenssl on NetBSD? I have a wierd problem that I think is OS specific. The client receives the first 16K of data, and nothing more. Usually. Sometimes repeatedly hitting Reload will result in the whole page coming over. > > It happens with nsopenssl 1.0 and 2.0 > It happens with database served pages (nspostgres) and static text files > It happens on the LAN and across the internet. > It happens on the local machine. > It happens with aolserver 3.4 and 3.4.2 > It happens with Internet Exploiter 5.5 and Netscape (unknown version, it's at home) > It happens on Windows clients and NetBSD clients and Linux clients. > > NetBSD is 1.5.2 on i386. > > I thought nsopenssl was closing the connection too soon but it appears not to be. > > I did some squirrely things when compiling openssl to get it to work, for example compiling it with -threads -D_REENTRANT. NetBSD does not support threads natively and I didn't tell openssl anything else about threads, so I don't know what this did, but it did let me get nsopenssl up and seeming to work. nsopenssl was compiled like aolserver, with PTL (Portable Thread Library) . > > Thanks in advance for any ideas... > > > > > Ian A. Harding > Programmer/Analyst II > Tacoma-Pierce County Health Department > (253) 798-3549 > mailto: [EMAIL PROTECTED] > > > >
[AOLSERVER] nsopenssl on NetBSD
Is anyone else using nsopenssl on NetBSD? I have a wierd problem that I think is OS specific. The client receives the first 16K of data, and nothing more. Usually. Sometimes repeatedly hitting Reload will result in the whole page coming over. It happens with nsopenssl 1.0 and 2.0 It happens with database served pages (nspostgres) and static text files It happens on the LAN and across the internet. It happens on the local machine. It happens with aolserver 3.4 and 3.4.2 It happens with Internet Exploiter 5.5 and Netscape (unknown version, it's at home) It happens on Windows clients and NetBSD clients and Linux clients. NetBSD is 1.5.2 on i386. I thought nsopenssl was closing the connection too soon but it appears not to be. I did some squirrely things when compiling openssl to get it to work, for example compiling it with -threads -D_REENTRANT. NetBSD does not support threads natively and I didn't tell openssl anything else about threads, so I don't know what this did, but it did let me get nsopenssl up and seeming to work. nsopenssl was compiled like aolserver, with PTL (Portable Thread Library) . Thanks in advance for any ideas... Ian A. Harding Programmer/Analyst II Tacoma-Pierce County Health Department (253) 798-3549 mailto: [EMAIL PROTECTED]
Re: [AOLSERVER] We've made a code change, would like opinions as to is this a good
In a message dated 12/8/2001 1:17:17 AM Eastern Standard Time, [EMAIL PROTECTED] writes: > In nsd/return.c we have modified the function > Ns_ConnReturnRedirect. Please note the additional block of > code marked with a "ZZZ BNA" comment. What this does is > return the user specified host name in preference to the > Location value. This solves our particular problem. It is > not a Virtual Hosting solution per se, but it does solve our > problem. > > Hello, The use of Host header makes sense to me and it's what we use for several sites here at AOL - perhaps it should just be the default in 4.0? As for the code changes, turns out there's an (undocumented) API in nsd/conn.c to set your own function to return the location. In 3.x (not sure when it arrived) it's: Ns_SetLocationProc(Ns_LocationProc *proc) and in 4.0 it's: Ns_SetLocationProc(char *server, Ns_LocationProc *proc) Note that because it was never documented I changed it to be (oddly) virtual server safe in the 2.x sense. An Ns_LocationProc is just a function which takes an Ns_Conn and returns a char *. Hope that helps, -Jim
