ns_conn has a number of issues/shortcomings:
host and protocol are and have ALWAYS been blank,
port is 0, unless non-standard port is used
location only uses the hostname configuration info, not the
actual Host header from the browser
also FRONT-END-HTTPS HTTP header from Front-End SSL
Gateways is not respected.
peerip does not respect X-Forwarded-For headers.
Along the same lines, ns_returnredirect doesn't prepend the right
location to relative urls.
-----Original Message-----
From: AOLserver Discussion [mailto:[EMAIL PROTECTED] On Behalf
Of Rick Cobb
Sent: Wednesday, January 16, 2008 10:57 PM
To: AOLSERVER@listserv.aol.com
Subject: [AOLSERVER] A question: why is ns_conn get protocol always
empty?
We figured this was just a long-standing bug in 3.4.2, so were surprised
to see it propagated into 4.5 as we ported up. Have the driver writers
simply given up on this field? We use both nssock & nsopenssl; the
field (in the Ns_Conn struct) is never populated. As I recall, nsperm
isn't great about using it, but our own permissions module certainly
would like to.
Thanks --
-- ReC
--
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 - 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.
