DO NOT REPLY [Bug 8731] - child segfaults 11 when using mod_proxy

[bu...@apache.org]

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=8731>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=8731

child segfaults 11 when using mod_proxy





------- Additional Comments From ceverett@ceverett.com  2002-05-02 14:10 -------
OK, I'm now quite sure this bug has more to do with the operating system than
apache.  

I was able to replicate the bug very easily.  On an *up to date* Debian Testing box,

1) set up 2 apaches, as you would if you were doing a front-end/back-end setup
for mod_perl.

2) set up the back end with a line saying "Listen 127.0.0.1:8080"

3) set up the front end with a virtual host like this:

NameVirtualHost 10.0.0.100
<VirtualHost 10.0.0.100>
  ServerName physemp-test.ceverett.com
  ServerAdmin ceverett@ceverett.com
  
  ProxyPass / http://127.0.0.1:8080/
  ProxyPassReverse / http://127.0.0.1:8080/
</VirtualHost>

At this point, being on that server, doing a "telnet localhost 8080",
then entering a simpe request should confimr that yiur back end is indeed alive.

Going into your browser and pulling up http://physemp-test.ceverett.com/
will kill several children on the front end server.

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