Re: mod_webapp apache2 problems:

2001-11-22 Thread jean-frederic clere

Brian P Millett wrote:
 
 Justin Erenkrantz wrote:
 
  On Wed, Nov 21, 2001 at 09:22:02AM -0600, Brian P Millett wrote:
   Quick Synopsis of error (apache 2.0):
   Syntax error on line 2 of /opt/apache/conf/mod_webapp.conf:
   Invalid port number (p1) No Port statement found
 
  Oooh, I bet it is related to the change that we committed to set
  port to 0 internally to represent that the port for the virtual
  server should be the port the connection actually comes in on.
  It's now done dynamically by the core at run-time per connection
  if port == 0 - which is the default for vhosts.  When the connection
  is actually received, the port will be the correct value.
 
  I'll take a gander at compiling webapp and posting a patch.  Can
  you verify with gdb or whatnot that wa_cvirtualhost is getting
  p=0?
 
 Put in a print statement, for the args going to wa_cvirtualhost:  n=shaka, p=0

Use something like:
+++
ServerName vtxclere.bcn.fsc.net:
+++
It works for me :))

 
 hope this helps
 
 --
 Brian Millett
 Enterprise Consulting Group   Shifts in paradigms
 (314) 205-9030   often cause nose bleeds.
 [EMAIL PROTECTED]   Greg Glenn
 
 --
 To unsubscribe, e-mail:   mailto:[EMAIL PROTECTED]
 For additional commands, e-mail: mailto:[EMAIL PROTECTED]

--
To unsubscribe, e-mail:   mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]




Re: mod_webapp apache2 problems:

2001-11-21 Thread Justin Erenkrantz

On Wed, Nov 21, 2001 at 09:22:02AM -0600, Brian P Millett wrote:
 Quick Synopsis of error (apache 2.0):
 Syntax error on line 2 of /opt/apache/conf/mod_webapp.conf:
 Invalid port number (p1) No Port statement found

Oooh, I bet it is related to the change that we committed to set
port to 0 internally to represent that the port for the virtual
server should be the port the connection actually comes in on.
It's now done dynamically by the core at run-time per connection
if port == 0 - which is the default for vhosts.  When the connection
is actually received, the port will be the correct value.

I'll take a gander at compiling webapp and posting a patch.  Can
you verify with gdb or whatnot that wa_cvirtualhost is getting
p=0?  -- justin


--
To unsubscribe, e-mail:   mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]




Re: mod_webapp apache2 problems:

2001-11-21 Thread jean-frederic clere

Justin Erenkrantz wrote:
 
 On Wed, Nov 21, 2001 at 09:22:02AM -0600, Brian P Millett wrote:
  Quick Synopsis of error (apache 2.0):
  Syntax error on line 2 of /opt/apache/conf/mod_webapp.conf:
  Invalid port number (p1) No Port statement found
 
 Oooh, I bet it is related to the change that we committed to set
 port to 0 internally to represent that the port for the virtual
 server should be the port the connection actually comes in on.
 It's now done dynamically by the core at run-time per connection
 if port == 0 - which is the default for vhosts.  When the connection
 is actually received, the port will be the correct value.
 
 I'll take a gander at compiling webapp and posting a patch.  Can
 you verify with gdb or whatnot that wa_cvirtualhost is getting
 p=0?  -- justin

p=0 :(
The port is svr-port the hostname svr-server_hostname (svr=cmd-server)
It is used before any connections...

 
 --
 To unsubscribe, e-mail:   mailto:[EMAIL PROTECTED]
 For additional commands, e-mail: mailto:[EMAIL PROTECTED]

--
To unsubscribe, e-mail:   mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]




Re: mod_webapp apache2 problems:

2001-11-21 Thread Brian P Millett

Justin Erenkrantz wrote:

 On Wed, Nov 21, 2001 at 09:22:02AM -0600, Brian P Millett wrote:
  Quick Synopsis of error (apache 2.0):
  Syntax error on line 2 of /opt/apache/conf/mod_webapp.conf:
  Invalid port number (p1) No Port statement found

 Oooh, I bet it is related to the change that we committed to set
 port to 0 internally to represent that the port for the virtual
 server should be the port the connection actually comes in on.
 It's now done dynamically by the core at run-time per connection
 if port == 0 - which is the default for vhosts.  When the connection
 is actually received, the port will be the correct value.

 I'll take a gander at compiling webapp and posting a patch.  Can
 you verify with gdb or whatnot that wa_cvirtualhost is getting
 p=0?

Put in a print statement, for the args going to wa_cvirtualhost:  n=shaka, p=0

hope this helps

--
Brian Millett
Enterprise Consulting Group   Shifts in paradigms
(314) 205-9030   often cause nose bleeds.
[EMAIL PROTECTED]   Greg Glenn




--
To unsubscribe, e-mail:   mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]