Re: [AOLSERVER] POLL: What's your preferred online communication medium?
>1) Name of medium (AOL IM, EFnet IRC, freenode IRC, Jabber, etc.) AIM, IRC, YHO, MSN >2) How many hours per day do you spend connected/available for chat on > this medium? Office hours. >3) What is your screen name/identifier that you typically use on this > medium? Varies per medium >4) (Optional) Why do you feel this medium would be best for hosting an > online chat? I feel that IRC would be the best medium b/c of a wide array of clients, and good logging support as well as a number of bots that could be used to quickly reference contents on say aolserver.com. /bart -- 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 email blank.
Re: [AOLSERVER] Java support in AOLserver
Last I tried nsjava on AOLserver I couldn't get it to work. I would have to dig through my notes to find out what the problem was. My impression is that nsjava hasn't seen much maintenance and that the last changes predate the release of AOLserver 4.0. /Bart -- 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 email blank.
Re: [AOLSERVER] ANN: New project leader for AOLserver
I have tried Tcl Dev Kit 3 recently and while it worked for the first connection to AOLserver, the Tcl debugger locked up AOLserver at the end of that connection. I followed the instructions at http://www.tcl.tk/man/aolserver3.0/tadp-ch6.htm /Bart -- 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 email blank.
Re: [AOLSERVER] ANN: New project leader for AOLserver
I recently setup an aolserver room at irc.freenode.net. Hardly anyone hangs out there these days, but the conversations there are being logged and are available from http://www.thecodemill.biz/services//aolserver/irc/. Maybe that IRC would be a viable alternatice to AIM? /Bart -- 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 email blank.
Re: [AOLSERVER] nsopenssl: permission denied
To answer my own question: Q: But why not to 192.168.1.2? A: Because previously I didn't explicitly specify the IP address in the nsopnessl driver section. Now that I do, it does work. Even though it previously inherited the same address from nssock? The log showed that it tried to bind to 192.168.1.2:443. /Bart -- 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 email blank.
Re: [AOLSERVER] nsopenssl: permission denied
Vlad, Lo and behold nsopenssl can listen to localhost:443. But why not to 192.168.1.2? To which nsopenssl 2.1 w/ aolserver 3.5 _could_ listen! /Bart -- 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 email blank.
Re: [AOLSERVER] nsopenssl: permission denied
Vlad, netstat -anp produces: Active Internet connections (servers and established) Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name tcp0 0 127.0.0.1: 0.0.0.0:* LISTEN 1377/nsd tcp0 0 0.0.0.0:139 0.0.0.0:* LISTEN 736/smbd tcp0 0 0.0.0.0:111 0.0.0.0:* LISTEN 484/portmap tcp0 0 192.168.1.2:80 0.0.0.0:* LISTEN 1377/nsd tcp0 0 0.0.0.0:113 0.0.0.0:* LISTEN 629/identd tcp0 0 0.0.0.0:21 0.0.0.0:* LISTEN 681/xinetd tcp0 0 0.0.0.0:22 0.0.0.0:* LISTEN 660/sshd tcp0 0 0.0.0.0:54320.0.0.0:* LISTEN 813/postmaster tcp0 0 192.168.1.2:139 192.168.0.3:1282 ESTABLISHED 15634/smbd tcp0 0 192.168.1.2:22 192.168.0.3:1239 ESTABLISHED 15417/sshd tcp0288 192.168.1.2:22 67.123.163.17:64527 ESTABLISHED 23521/sshd udp0 0 127.0.0.1:1025 127.0.0.1:1025 ESTABLISHED 813/postmaster udp0 0 192.168.1.2:137 0.0.0.0:* 741/nmbd udp0 0 0.0.0.0:137 0.0.0.0:* 741/nmbd udp0 0 192.168.1.2:138 0.0.0.0:* 741/nmbd udp0 0 0.0.0.0:138 0.0.0.0:* 741/nmbd udp0 0 127.0.0.1:4562 0.0.0.0:* 15634/smbd udp0 0 0.0.0.0:111 0.0.0.0:* 484/portmap udp0 0 192.168.1.2:123 0.0.0.0:* 10049/ntpd udp0 0 127.0.0.1:123 0.0.0.0:* 10049/ntpd udp0 0 0.0.0.0:123 0.0.0.0:* 10049/ntpd Active UNIX domain sockets (servers and established) Proto RefCnt Flags Type State I-Node PID/Program name Path unix 2 [ ACC ] STREAM LISTENING 1261 813/postmaster /tmp/.s.PGSQL.5432 unix 2 [ ACC ] STREAM LISTENING 545668 15417/sshd /tmp/ssh-XXzfIdML/agent.15417 unix 8 [ ] DGRAM805465/syslogd /dev/log unix 3 [ ] STREAM CONNECTED 625670 1396/postgres: nsad /tmp/.s.PGSQL.5432 unix 3 [ ] STREAM CONNECTED 625669 1377/nsd unix 3 [ ] STREAM CONNECTED 625638 1377/nsd unix 3 [ ] STREAM CONNECTED 625637 1377/nsd unix 3 [ ] STREAM CONNECTED 625620 1384/postgres: nsad /tmp/.s.PGSQL.5432 unix 3 [ ] STREAM CONNECTED 625619 1377/nsd unix 3 [ ] STREAM CONNECTED 625618 1383/postgres: nsad /tmp/.s.PGSQL.5432 unix 3 [ ] STREAM CONNECTED 625617 1377/nsd unix 3 [ ] STREAM CONNECTED 625616 1382/postgres: nsad /tmp/.s.PGSQL.5432 unix 3 [ ] STREAM CONNECTED 625615 1377/nsd unix 3 [ ] STREAM CONNECTED 625612 1377/nsd unix 3 [ ] STREAM CONNECTED 625611 1377/nsd unix 2 [ ] DGRAM85087 10049/ntpd unix 2 [ ] DGRAM1105 711/crond unix 2 [ ] DGRAM1047 681/xinetd unix 2 [ ] DGRAM975629/identd unix 2 [ ] DGRAM962617/automount unix 2 [ ] DGRAM817470/klogd unix 2 [ ] STREAM CONNECTED 5131/init [3] As you can see port 443 is still available. /Bart -- 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 email blank.
Re: [AOLSERVER] nsopenssl: permission denied
Adding NsWaitDriversStartup() didn't help. The strang thing is that port 80 works fine, just 443 doesn't get permission: [04/May/2004:12:43:33][1377.1024][-main-] Error: nsopenssl: failed to listen on 192.168.1.2:443: Permission denied [04/May/2004:12:43:33][1377.1024][-main-] Notice: nssock: listening on 192.168.1.2:80 /Bart -- 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 email blank.
Re: [AOLSERVER] nsopenssl: permission denied
On Mon, 3 May 2004 15:32:24 -0400, Scott Goodwin <[EMAIL PROTECTED]> wrote:
>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 name of the thread). I trust the error message
>because it's coming from the OS; the driver code is very
>straightforward. So my guess is that you really aren't root at start
>time.
I am most certainly root.
>Post the OS make, model and version (my guess is you're using Solaris),
Redhat 7.1 on x486
>the command line that you use to start the server
#! /bin/sh
export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/usr/local/pgsql/lib:/usr/local/ssl/lib
exec /usr/local/aolserver/bin/nsd -it /etc/aolserver/7-sisters.com.tcl -B
/etc/aolserver/7-sisters.com.bnd -u nsadmin -g web
where 7-sisters.com.bnd contains:
192.168.1.2:80
192.168.1.2:443
>and your nsd.tcl file
>with any sensitive stuff removed.
ns_log notice "nsd.tcl: starting to read config file..."
set httpport 80
set httpsport 443
set hostname www.7-sisters.com
set address 192.168.1.2
set homedir /usr/local/aolserver
set bindir ${homedir}/bin
set logdir /var/log/aolserver
set rundir /var/run/aolserver
if [file isdirectory "$homedir/servers/7-sisters.com"] {
set server "7-sisters.com"
set servername "${hostname} server"
set pageroot /web/${server}/www
}
set directoryfile index.adp,index.tcl,index.php,index.html,index.htm
set sslkeyfile
${homedir}/servers/${server}/modules/nsopenssl/www.7-sisters.com.key
set sslcertfile
${homedir}/servers/${server}/modules/nsopenssl/www.7-sisters.com.crt
ns_section "ns/parameters"
ns_param User nsadmin
ns_param Group nsadmin
ns_param home $homedir
ns_param pidfile $rundir/nsd.pid
ns_param debugfalse
ns_param MailHost mail.7-sisters.com
ns_param ServerLog${logdir}/${server}-error.log
ns_param LogRoll on
ns_param MaxBackup 9
ns_section "ns/threads"
ns_param mutexmeter true ;# measure lock contention
ns_param stacksize [expr 256*1024] ;# Per-thread stack size for hungry C
modules. Increased to 256 for PHP.
ns_section "ns/servers"
ns_param $server $servername
ns_section "ns/server/${server}"
ns_param directoryfile$directoryfile
ns_param pageroot $pageroot
ns_param globalstats false ;# Enable built-in statistics
ns_param urlstats false ;# Enable URL statistics
ns_param maxurlstats 1000 ;# Max number of URL's to do
stats on
ns_param enabletclpages true ;# Parse tcl files in
# pageroot (dangerous)
ns_param maxthreads 5
ns_param minthreads 5
ns_section "ns/server/${server}/module/nssock"
ns_param port $httpport
ns_param hostname $hostname
ns_param address $address
ns_section ns/server/${server}/module/nsopenssl/sslcontexts
ns_param ${server}_ctx "SSL context for regular user access"
ns_param ${server}_client_ctx "SSL context for outgoing script socket
connections"
ns_section ns/server/${server}/module/nsopenssl/defaults
ns_param server ${server}_ctx
ns_param client ${server}_client_ctx
ns_section ns/server/${server}/module/nsopenssl/sslcontext/${server}_ctx
ns_param Role server
ns_param CertFile ${sslcertfile}
ns_param KeyFile ${sslkeyfile}
ns_param CADir ca
ns_param CAFile ca/freesslca.crt
ns_param ModuleDir ${homedir}/servers/${server}/modules/nsopenssl/
ns_param Protocols "SSLv2, SSLv3, TLSv1"
ns_param CipherSuite "ALL:!ADH:RC4+RSA:+HIGH:+MEDIUM:+LOW:+SSLv2:+EXP"
ns_param PeerVerify false
ns_param PeerVerifyDepth 3
ns_param Trace false
ns_param SessionCache true
ns_param SessionCacheID 1
ns_param SessionCacheSize 512
ns_param SessionCacheTimeout 300
ns_section ns/server/${server}/module/nsopenssl/sslcontext/${server}_client_ctx
ns_param Role client
ns_param CertFile ${sslcertfile}
ns_param KeyFile ${sslkeyfile}
ns_param CADir ca
ns_param CAFile ca/freesslca.crt
ns_param ModuleDir ${homedir}/servers/${server}/modules/nsopenssl/
ns_param Protocols "SSLv2, SSLv3, TLSv1"
ns_param CipherSuite "ALL:!ADH:RC4+RSA:+HIGH:+MEDIUM:+LOW:+SSLv2:+EXP"
ns_param PeerVerify false
ns_param PeerVerifyDepth 3
ns_param Trace false
ns_param SessionCache true
ns_param SessionCacheID 1
ns_param SessionCacheSize 512
ns_param SessionCacheTimeout 300
ns_section ns/server/${server}/module/nsopenssl/ssldrivers
ns_param ${server}_drv "Driver for regular user access"
ns_section ns/server/${server}/module/nsopenssl/ssldr
Re: [AOLSERVER] nsopenssl: permission denied
Hmm, I've changed the max/minthreads in ns/servers/server1 to no avail. Scott, do you have any suggestions? /Bart On Mon, 3 May 2004 02:49:47 -0400, Chris Davies <[EMAIL PROTECTED]> wrote: >I had a very very similar problem. > >ns_param maxthreads 5 >ns_param minthreads 5 > >with minthreads 0, (and sometimes 1 or 2) it exhibited the same >behavior. > >On Mon, 2004-05-03 at 02:02, Bart Teeuwisse wrote: >> Notice: prebind: bound: 192.168.1.2:80 >> Notice: prebind: bound: 192.168.1.2:443 >>3471:[02/May/2004:21:28:29][21728.1024][-main-] Error: nsopenssl: failed >> to listen on 192.168.1.2:443: Permission denied -- 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 email blank.
[AOLSERVER] nsopenssl: permission denied
I've been staring at this problem for a while now and can't seem to place my finger on it. I've compiled nsopenssl 3.x (CVS HEAD) against OpenSSL 0.9.7d, loading nsopenssl in AOLserver 4.0 r3 appears to go flawless. Except for a OpenSSL memory callback warning. The port nsopenssl listens to (443) has been pre-bound but in the end openssl fails to listen to the port because permission is denied. Root started AOLserver w/ same user and group (nsadmin/web) which previously worked well with nsopenssl 2.x and AOLserver 3.x. See the relvant entries from the log below: Notice: prebind: bound: 192.168.1.2:80 Notice: prebind: bound: 192.168.1.2:443 42:[02/May/2004:21:27:36][21728.1024][-main-] Notice: modload: loading '/usr/local/aolserver/bin/nsopenssl.so' 43:[02/May/2004:21:27:37][21728.1024][-main-] Warning: nsopenssl: OpenSSL memory callbacks failed in InitOpenSSL 44:[02/May/2004:21:27:37][21728.1024][-main-] Notice: nsopenssl (7-sisters.com): loading SSL context '7-sisters.com_ctx' 45:[02/May/2004:21:27:37][21728.1024][-main-] Notice: nsopenssl (7-sisters.com): '7-sisters.com_ctx' ciphers loaded successfully 46:[02/May/2004:21:27:37][21728.1024][-main-] Notice: nsopenssl (7-sisters.com): '7-sisters.com_ctx' using SSLv2 protocol 47:[02/May/2004:21:27:37][21728.1024][-main-] Notice: nsopenssl (7-sisters.com): '7-sisters.com_ctx' using SSLv3 protocol 48:[02/May/2004:21:27:37][21728.1024][-main-] Notice: nsopenssl (7-sisters.com): '7-sisters.com_ctx' using TLSv1 protocol 49:[02/May/2004:21:27:37][21728.1024][-main-] Notice: nsopenssl (7-sisters.com): '7-sisters.com_ctx' key loaded successfully 50:[02/May/2004:21:27:37][21728.1024][-main-] Notice: nsopenssl (7-sisters.com): '7-sisters.com_ctx' certificate loaded successfully 51:[02/May/2004:21:27:37][21728.1024][-main-] Notice: nsopenssl (7-sisters.com): '7-sisters.com_ctx' CA file loaded successfully 52:[02/May/2004:21:27:37][21728.1024][-main-] Notice: 7-sisters.com_ctx (nsopenssl): session cache is turned on for sslcontext '7-sisters.com' 53:[02/May/2004:21:27:37][21728.1024][-main-] Notice: nsopenssl (7-sisters.com): loading SSL context '7-sisters.com_client_ctx' 54:[02/May/2004:21:27:37][21728.1024][-main-] Notice: nsopenssl (7-sisters.com): '7-sisters.com_client_ctx' ciphers loaded successfully 55:[02/May/2004:21:27:37][21728.1024][-main-] Notice: nsopenssl (7-sisters.com): '7-sisters.com_client_ctx' using SSLv2 protocol 56:[02/May/2004:21:27:37][21728.1024][-main-] Notice: nsopenssl (7-sisters.com): '7-sisters.com_client_ctx' using SSLv3 protocol 57:[02/May/2004:21:27:37][21728.1024][-main-] Notice: nsopenssl (7-sisters.com): '7-sisters.com_client_ctx' using TLSv1 protocol 58:[02/May/2004:21:27:37][21728.1024][-main-] Notice: nsopenssl (7-sisters.com): '7-sisters.com_client_ctx' key loaded successfully 59:[02/May/2004:21:27:37][21728.1024][-main-] Notice: nsopenssl (7-sisters.com): '7-sisters.com_client_ctx' certificate loaded successfully 60:[02/May/2004:21:27:37][21728.1024][-main-] Notice: nsopenssl (7-sisters.com): '7-sisters.com_client_ctx' CA file loaded successfully 61:[02/May/2004:21:27:37][21728.1024][-main-] Notice: 7-sisters.com_client_ctx (nsopenssl): session cache is turned on for sslcontext '7-sisters.com' 62:[02/May/2004:21:27:37][21728.1024][-main-] Notice: nsopenssl (7-sisters.com): default SSL context for server is 7-sisters.com_ctx 64:[02/May/2004:21:27:37][21728.1024][-main-] Notice: nsopenssl (7-sisters.com): default SSL context for client is 7-sisters.com_client_ctx 66:[02/May/2004:21:27:37][21728.1024][-main-] Notice: nsopenssl (7-sisters.com): loading '7-sisters.com_drv' SSL driver 3471:[02/May/2004:21:28:29][21728.1024][-main-] Error: nsopenssl: failed to listen on 192.168.1.2:443: Permission denied /Bart -- 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 email blank.
[AOLSERVER] #aolserver IRC channel set up
While I really appreciate and value this list, there are times when the instant gratification of IRC is more appropriate. So I went ahead and claimed #aolserver at irc.freenode.org (irc://irc.freenode.net/#aolserver) and setup a logging bot for it. The logs are available from: http://www.thecodemill.biz/services/aolserver/irc/ /Bart -- 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 email blank.
[AOLSERVER] ns_respond locks AOLServer
Export / download of data files from AOLServer causes the webserver to lock up.The problem seems to be with ns_respond. Where possible I've replaced those with ns_return as that does work. But ns_respond is needed to return file contents instead of text stings. Has anyone else observed this behaviour w/ AOLServer 4.x (I've tried all releases as well as CVS HEAD.) /Bart -- 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 email blank.
Re: [AOLSERVER] Server doesn't recognize directories starting with +
Thanks for gzipping the patch Stephen, that did the trick. Works like a charm with aforementioned tarball as well as CVS HEAD. /Bart -- 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 email blank.
Re: [AOLSERVER] Server doesn't recognize directories starting with +
Oops,
a cut and paste mistake. What I ment to post is:
Applying Stephen's patch to the 2003-11-09 tarball yields:
513 [EMAIL PROTECTED]/tmp> tar zxf ~/tmp/aolserver-4.0-src.tar.gz
514 [EMAIL PROTECTED]/tmp> cd aolserver-4.0
515 [EMAIL PROTECTED]/tmp/aolserver-4.0> patch -p1 -b <
../aolserver-4.0-plus-sign-encoding.patch
patching file include/ns.h
patching file nsd/urlencode.c
Hunk #2 FAILED at 131.
Hunk #4 FAILED at 249.
Hunk #5 FAILED at 268.
Hunk #6 FAILED at 319.
Hunk #8 FAILED at 393.
5 out of 8 hunks FAILED -- saving rejects to file nsd/urlencode.c.rej
patching file nsd/form.c
Hunk #1 FAILED at 250.
1 out of 1 hunk FAILED -- saving rejects to file nsd/form.c.rej
nsd/urlencode.c.rej:
***
*** 123,132
/*
*--
*
- * Ns_EncodeUrlWithEncoding --
*
* Take a URL and encode any non-alphanumeric characters into
- * %hexcode
*
* Results:
* A pointer to the encoded string (which is part of the
--- 131,140
/*
*--
*
+ * Ns_EncodeUrlWithEncoding, Ns_EncodeUrlCharset --
*
* Take a URL and encode any non-alphanumeric characters into
+ * %hexcode.
*
* Results:
* A pointer to the encoded string (which is part of the
***
*** 171,177
q = dsPtr->string + i;
p = string;
while ((i = UCHAR(*p)) != 0) {
-if (UCHAR(*p) == ' ') {
*q++ = '+';
} else if (enc[i].str == NULL) {
*q++ = *p;
--- 249,255
q = dsPtr->string + i;
p = string;
while ((i = UCHAR(*p)) != 0) {
+if (UCHAR(*p) == ' ' && scheme == FORM_ENCODING) {
*q++ = '+';
} else if (enc[i].str == NULL) {
*q++ = *p;
***
*** 190,230
return dsPtr->string;
}
-
/*
*--
*
- * Ns_EncodeUrlCharset --
*
- * Take a URL and encode any non-alphanumeric characters into
- * %hexcode
*
* Results:
- * A pointer to the encoded string (which is part of the
- * passed-in DString's memory)
*
* Side effects:
- * Encoded URL will be copied to given dstring.
*
*--
*/
char *
- Ns_EncodeUrlCharset(Ns_DString *dsPtr, char *string, char *charset)
{
- Tcl_Encoding encoding = GetUrlEncoding(charset);
- return Ns_EncodeUrlWithEncoding(dsPtr, string, encoding);
}
/*
*--
*
- * Ns_DecodeUrlCharset --
*
- * Decode an encoded URL (with %hexcode, etc.).
*
* Results:
* A pointer to the dstring's value, containing the decoded
--- 268,312
return dsPtr->string;
}
/*
*--
*
+ * Ns_DecodeUrlWithEncoding, Ns_DecodeUrlCharset --
*
+ * Decode an encoded URL (with %hexcode).
*
* Results:
+ * A pointer to the dstring's value, containing the decoded
+ * URL.
*
* Side effects:
+ * Decoded URL will be copied to given dstring.
*
*--
*/
char *
+ Ns_DecodeUrlWithEncoding(Ns_DString *dsPtr, char *string, Tcl_Encoding
encoding)
{
+ return DecodeWithEncoding(dsPtr, string, encoding, URL_ENCODING);
+ }
+ char *
+ Ns_DecodeUrlCharset(Ns_DString *dsPtr, char *string, char *charset)
+ {
+ Tcl_Encoding encoding = GetUrlEncoding(charset);
+ return Ns_DecodeUrlWithEncoding( dsPtr, string, encoding );
}
+
/*
*--
*
+ * Ns_DecodeFormWithEncoding, Ns_DecodeFormCharset --
*
+ * Decode encoded form data (with %hexcode, etc.).
*
* Results:
* A pointer to the dstring's value, containing the decoded
***
*** 237,257
*/
char *
- Ns_DecodeUrlCharset(Ns_DString *dsPtr, char *string, char *charset)
{
Tcl_Encoding encoding = GetUrlEncoding(charset);
return Ns_DecodeUrlWithEncoding( dsPtr, string, encoding );
}
-
/*
*--
*
- * Ns_DecodeUrlWithEncoding --
*
- * Decode an encoded URL (with %hexcode, etc.).
*
* Results:
* A pointer to the dstring's value, containing the decoded
--- 319,347
*/
char *
+ Ns_DecodeFormWithEncoding(Ns_DString *dsPtr, char *string, Tcl_Encoding
encoding)
+ {
+ return DecodeWithEncoding(dsPtr, string, encoding, FORM_ENCODING);
+ }
+
+ char *
+ Ns_DecodeFormCharset(Ns_DString *dsPtr, char *string, char *charset)
{
Tcl_Encoding encoding = GetUrlEncoding(charset);
return Ns_DecodeUrlWithEncoding( dsPtr, string, encoding );
}
/*
*---
Re: [AOLSERVER] Server doesn't recognize directories starting with +
***
*** 250,259
*v = '\0';
}
Ns_DStringTrunc(&kds, 0);
-k = Ns_DecodeUrlWithEncoding(&kds, k, encoding);
if (v != NULL) {
Ns_DStringTrunc(&vds, 0);
-Ns_DecodeUrlWithEncoding(&vds, v+1, encoding);
*v = '=';
v = vds.string;
}
--- 250,259
*v = '\0';
}
Ns_DStringTrunc(&kds, 0);
+k = Ns_DecodeFormWithEncoding(&kds, k, encoding);
if (v != NULL) {
Ns_DStringTrunc(&vds, 0);
+Ns_DecodeFormWithEncoding(&vds, v+1, encoding);
*v = '=';
v = vds.string;
}
--
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 email blank.
Re: [AOLSERVER] Server doesn't recognize directories starting with +
Stephen, against which version of AOLserver 4.0 did you make the patch? The patch is not lining up against the tarball of 2003-11-09 as available from sourceforge. Neither does it match the current CVS HEAD. /Bart -- 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 email blank.
Re: [AOLSERVER] Server doesn't recognize directories starting with +
Tom, your experience differs from mine. I'm experiencing problems with +directories on AOLserver 4.1 (CVS HEAD). Maybe you are running another version? /Bart -- 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 email blank.
Re: [AOLSERVER] Server doesn't recognize directories starting with +
Jim, you hit the nail on the head. http://dev.thecodemill.biz/%2Btest/ does return a directory listing. But can the server ensure that clients will encode plus signs? Or can AOLserver determine when to replace + with a space and when to leave as is? /Bart -- 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 email blank.
[AOLSERVER] Server doesn't recognize directories starting with +
Fastpath.c doesn't recognize directories starting with a plus sign (+). Thus _ns_dirlist is never called to return the content of the directory. This is important to me as I'm trying to setup AOLserver to host GNU Arch (http://www.gnu.org/software/gnu-arch/) archives. Arch makes use of directories called ++revision-lick and +contents to name a couple examples. Lacking the necessary C skills, I'd like to ask those who do posses them, is it a bug that fastpath.c doesn't recognize directory names starting with a plus sign? If not what is needed to fix it? /Bart -- 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 email blank.
Re: [AOLSERVER] How to use nsopenssl 3.x?
Thanks for explaining the nsopenssl config section Scott. Let me give you some feedback of what I've found so far. Nsopenssl appears to perform well for the most part. However, nsopenssl writes several empty error messages to the log. Can't tell what they are related to. More importantly though making a client connection using ns_httpsopen results in the following error: [29/Sep/2003:18:14:58][20762.65541][-conn:demo::0] Error: : nsopenssl: error creating sslconn->ssl structure The server subsequently hangs and doesn't respond to requests anymore. /Bart -- 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 email blank.
[AOLSERVER] How to use nsopenssl 3.x?
I'd like to experiment with nsopenssl 3.x on AOLServer 4.x. I'm aware that nsopenssl 3.x isn't production ready yet. Still, I'd like run some experiments but I'm not quite clear how to use the new design. Following the README file, I've configured nsd.tcl as per the 2.x instructions. However, I'm at a loss how to define contexts and drivers for virtual servers. The Design paragraph at the end of the README file mentions how the new workflow uses the contexts and drivers defined in nsd.tcl but doesn't include examples. Scott, would you be so kind to enlighten me? Thanks, /Bart -- 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 email blank.
[AOLSERVER] Using & to seperate query vars
Running some pages through a the W3.org HTML validator I learned that the HTML 4.01 Transitional standard requires query vars to be separated by & instead of &. E.g. http://.thecodemill.biz/vars?bla=bladibla&blurb=blabla should be http://.thecodemill.biz/vars?bla=bladibla&blurb=blabla Yet if you follow the above links you'll notice that AOLserver does not handle query vars separated by & very well. Rather than treating & as an entity. AOLserver replaces the & character which results in a var named 'amp;blurb' instead of 'blurb' Google for example treats & and & separated queries the same. Shouldn't AOLserver be patched to stay standards compliant? /Bart
