Re: [AOLSERVER] Fwd: AOLServer 4
We're trying to get in touch with the PHP team to address. This is one of the potential side effects of moving to 4.0 from prior 3.x versions since virtual server support is now back. Pretty easy to address - be sure to check out Mark's porting document: http://aolserver.sourceforge.net/docs/devel/c/ as4_moduleportingguide.html. Stay tuned! - Nathan On Friday, March 28, 2003, at 10:17 AM, Andrey Chichak wrote: It works! But only when for 1 virtual host enabled. -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list: http://www.aolserver.com/listserv.html List information and options: http://listserv.aol.com/
Re: [AOLSERVER] Fwd: AOLServer 4
On Thursday, March 27, 2003, at 02:22 AM, Andrey Chichak wrote: I want migrate from apache+php to aolserver+python :o) Do you know about PyWX? http://pywx.idyll.org/ -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list: http://www.aolserver.com/listserv.html List information and options: http://listserv.aol.com/
Re: [AOLSERVER] Fwd: AOLServer 4
I want migrate from apache+php to aolserver+python :o) Ehrm, if you are porting anyway, why not go with the native language for AOLserver? Bas. -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list: http://www.aolserver.com/listserv.html List information and options: http://listserv.aol.com/
Re: [AOLSERVER] Fwd: AOLServer 4
With this config file I became understand AOLserver configuring, but some
problem is here.
Line :
ns_paramenabletclpagestrue ;# allow .tcl files to be parsed
has to be in
ns_section ns/server/${servername}
Yes, my mistake.
I had modified my version of modules/tcl/file.tcl to look for enabletclpages
on a per virtual server basis.
And one more problem :
PHP does not work with virtual hosts enabled :o(
Bah! you can do anything you want in Tcl, if you can't it's not worth doing!
;-)
--
AOLserver - http://www.aolserver.com/
To Remove yourself from this list: http://www.aolserver.com/listserv.html
List information and options: http://listserv.aol.com/
Re: [AOLSERVER] Fwd: AOLServer 4
With this config file I became understand AOLserver configuring, but some
problem is here.
Line :
ns_paramenabletclpagestrue ;# allow .tcl files to be parsed
has to be in
ns_section ns/server/${servername}
And one more problem :
PHP does not work with virtual hosts enabled :o(
Andrey Chichak.
--
AOLserver - http://www.aolserver.com/
To Remove yourself from this list: http://www.aolserver.com/listserv.html
List information and options: http://listserv.aol.com/
Re: [AOLSERVER] Fwd: AOLServer 4
On Wed, 26 Mar 2003 14:09:04 -, Tim Moss [EMAIL PROTECTED] wrote: And one more problem : PHP does not work with virtual hosts enabled :o( Bah! you can do anything you want in Tcl, if you can't it's not worth doing! ;-) I want migrate from apache+php to aolserver+python :o) Andrey -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list: http://www.aolserver.com/listserv.html List information and options: http://listserv.aol.com/
Re: [AOLSERVER] Fwd: AOLServer 4
I agree with Peter here on every point - I've got most of them if not all of
them working in practice.
The only thing I'd add which he didn't make explicitly clear is that you can
have sites with the same names, but different ports using different virtual
servers if you so wish.
If you want an example config file then Peter kindly posted some examples to
this list a couple of weeks ago.
If you can't find them, then please just ask I'll post mine (In fact Nathan
should already have it as I recently emailed it to him)
-Original Message-
From: AOLserver Discussion [mailto:[EMAIL PROTECTED]]On Behalf
Of Peter M. Jansson
Sent: Sunday, February 09, 2003 5:02 AM
To: [EMAIL PROTECTED]
Subject: Re: [AOLSERVER] Fwd: AOLServer 4
On Sat, 8 Feb 2003, Nathan Folkman wrote:
Can someone who has actually used these features help Chris out? Thanks!
1. Can you specify a document root for each host
Yes, and, in fact, you must. Each virtual server is separate, and there
won't be any inheritence of features between them, so if you want a
virtual server to have a particular feature, you must explicitly enable
it.
2. Are all sourced Tcl files available to all hosts or can you
limit this via config
Not necessarily. Each virtual server gets its own Tcl interpreters. Any
Tcl you have in ${AOLSERVER_ROOT}/modules/tcl will be sourced by all
virtual servers, per the usual instructions (stuff in the dir is done
alphabetically; subdirs are only loaded if there is a ns_param subdir
Tcl in the modules section for the virtual). Stuff in
${AOLSERVER_ROOT}/servers/$server/modules/tcl is strictly per-virtual
server.
3. Can you do name and ip based virtual hosting
Yes. You can load the nssock module globally, which enables host-based
virtual servers. Additionally, you can load nssock on a per-module basis
and nail a particular virtual server to a particular IP address. I don't
believe you have a choice about which nssock instance gets the name-based
virtual servers; it's always the global one.
Scott, want to comment on nsopenssl?
Re: [AOLSERVER] Fwd: AOLServer 4
On Sat, 8 Feb 2003, Nathan Folkman wrote:
Can someone who has actually used these features help Chris out? Thanks!
1. Can you specify a document root for each host
Yes, and, in fact, you must. Each virtual server is separate, and there
won't be any inheritence of features between them, so if you want a
virtual server to have a particular feature, you must explicitly enable
it.
2. Are all sourced Tcl files available to all hosts or can you
limit this via config
Not necessarily. Each virtual server gets its own Tcl interpreters. Any
Tcl you have in ${AOLSERVER_ROOT}/modules/tcl will be sourced by all
virtual servers, per the usual instructions (stuff in the dir is done
alphabetically; subdirs are only loaded if there is a ns_param subdir
Tcl in the modules section for the virtual). Stuff in
${AOLSERVER_ROOT}/servers/$server/modules/tcl is strictly per-virtual
server.
3. Can you do name and ip based virtual hosting
Yes. You can load the nssock module globally, which enables host-based
virtual servers. Additionally, you can load nssock on a per-module basis
and nail a particular virtual server to a particular IP address. I don't
believe you have a choice about which nssock instance gets the name-based
virtual servers; it's always the global one.
Scott, want to comment on nsopenssl?
