Re: [AOLSERVER] AOLserver, nginx, and port numbers

2011-02-14 Thread aT
or you could do in nginx proxy_redirect http://shared.furfly.net:8082 http://shared.furfly.net; On 02/03/2011 11:20 AM, Janine Ohmer wrote: Thanks, that did the trick! It works in the nsopenssl section also. janine On Feb 2, 2011, at 7:08 PM, Jeff Rogers wrote: It doesn't seem to be

Re: [AOLSERVER] AOLserver, nginx, and port numbers

2011-02-03 Thread Alexey Pechnikov
For virtual hosting I use this wrapper for ns_conn function: rename ns_conn _ns_conn proc ns_conn {args} { set host [string tolower [ns_set get [ns_conn headers] Host]] if {[string match [lindex $args 0] host]} { regexp {[^:]+} $host host

[AOLSERVER] AOLserver, nginx, and port numbers

2011-02-02 Thread Janine Ohmer
I'm moving some sites onto an Amazon EC2 instance, which has only one IP address, so I'm using nginx to make this work. The websites (both Apache and AOLserver) are running on various internal ports. The site I'm having trouble with is running on http://localhost:8082 internally, and on

Re: [AOLSERVER] AOLserver, nginx, and port numbers

2011-02-02 Thread Jeff Rogers
It doesn't seem to be documented, but you can set a 'location' parameter for nssock that will override this: ns_section ns/server/server1/module/nssock ns_param port 8082 ns_param location http://shared.furfly.net Cheers, -J Janine Ohmer wrote: My problem is the value returned by [ns_conn

Re: [AOLSERVER] AOLserver, nginx, and port numbers

2011-02-02 Thread Janine Ohmer
Thanks, that did the trick! It works in the nsopenssl section also. janine On Feb 2, 2011, at 7:08 PM, Jeff Rogers wrote: It doesn't seem to be documented, but you can set a 'location' parameter for nssock that will override this: ns_section ns/server/server1/module/nssock ns_param port