httpd-bugs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 24331] - SSLPassPhraseDialog exec: always default port in argv
Date Tue, 07 Dec 2004 03:02:31 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=24331>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=24331





------- Additional Comments From warp-9.9@usa.net  2004-12-07 04:02 -------
(In reply to comment #10)
> Ah, OK, from the config fragments you sent me, the difference is whether or not
> the port is explicitly configured in the ServerName directive.  With "ServerName
> www.foo.com" s->port ends up as zero, indeed, clearing the s->port setting from
> the address in the VirtualHost directive.

Ok, so the question I guess, should the port be taken from the <VirtualHost
ip:port> (if specified), or ServerName host:port?  Should it be checked that it
is specified nowhere (ok, assume whatever you're listening on, default port 80
or 443, however that is determined), both places the same (ok: if listening),
one place but not the other (ok if listening), or in both places if different
(error, regardless of listening).  How does it get the IP address correctly and
not always assume one IP address, when I listen to * or 0.0.0.0 ?  Should I try
my hand fiddling with vhost.c?  Or should there be an error raised if a port is
specified in one place but not the other?

My own order of preference (regarding ip:port in VirtualHost and ServerName
directives):

1) a) defined nowhere, use default
   b) defined in VirtualHost, not ServerName, use VirtualHost if Listening to
ip:port
   c) defined in ServerName, not VirtualHost, use ServerName if Listening to ip:port
   d) not defined in VirtualHost or ServerName, use default
   e) defined in both VirtualHost and ServerName, but different, error out with
helpful message

2) If not listening to a default port, port must be specified and the same in
both VirtualHost and ServerName
   a) port specified in VirtualHost but not ServerName, error
   b) port not specified in VirtualHost, but is defined in ServerName, error
   c) specified in VirtualHost and ServerName, but different, error

The first is more forgiving of config errors but maybe harder to code?  The
second is simpler to code, but not so forgiving of config errors and requires
somewhat redundant config.  I specify the port once for the Listen, once for the
VirtualHost, so why doesn't ServerName inherit from the virtualHost in which it
resides?

And, thanks a lot for the help with this little snafu!

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org


Mime
View raw message