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=7985>.
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=7985
Broken functionality in Apache::Status when proxied
Summary: Broken functionality in Apache::Status when proxied
Product: Apache httpd-1.3
Version: 1.3.24
Platform: PC
OS/Version: Linux
Status: NEW
Severity: Minor
Priority: Other
Component: Other mods
AssignedTo: bugs@httpd.apache.org
ReportedBy: brian.bothwell@wisdomtools.com
We run our web-app with a light mod_proxy front end to handle static requests
and pass all Perl stuff to backend mod_perl servers, and noticed that with this
setup the "perl-status" feature of server-status doesn't work correctly given
our setup.
We have the mod_proxy server using configured like so:
ProxyPass /test1 http://localhost:8000
ProxyPassReverse /test1 http://localhost:8000
so the URL of the mod_perl site is:
http://ourserver.com/test1/script.cgi
We have the backend mod_perl servers configured with Apache::Status like so:
<Location /perl-status>
SetHandler perl-script
PerlHandler Apache::Status
Order deny,allow
Deny from all
Allow from .wisdomtools.com localhost
</Location>
When we access perl-status thru the proxy, the URL is:
http://ourserver.com/test1/perl-status
which works, but if we access one of the modules of perl-status, it attempts to
access this:
http://ourserver.com/perl-status?symdump
which doesn't work since the "test1" is missing, so I have taken to inserting
the "test1" into the URL manually. Not a showstopper, but annoying none the
less.
I may be missing some config to fix this, so this may not actually be a bug.
Thanks,
-Brian
---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=7985>.
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=7985
Broken functionality in Apache::Status when proxied
Summary: Broken functionality in Apache::Status when proxied
Product: Apache httpd-1.3
Version: 1.3.24
Platform: PC
OS/Version: Linux
Status: NEW
Severity: Minor
Priority: Other
Component: Other mods
AssignedTo: bugs@httpd.apache.org
ReportedBy: brian.bothwell@wisdomtools.com
We run our web-app with a light mod_proxy front end to handle static requests
and pass all Perl stuff to backend mod_perl servers, and noticed that with this
setup the "perl-status" feature of server-status doesn't work correctly given
our setup.
We have the mod_proxy server using configured like so:
ProxyPass /test1 http://localhost:8000
ProxyPassReverse /test1 http://localhost:8000
so the URL of the mod_perl site is:
http://ourserver.com/test1/script.cgi
We have the backend mod_perl servers configured with Apache::Status like so:
<Location /perl-status>
SetHandler perl-script
PerlHandler Apache::Status
Order deny,allow
Deny from all
Allow from .wisdomtools.com localhost
</Location>
When we access perl-status thru the proxy, the URL is:
http://ourserver.com/test1/perl-status
which works, but if we access one of the modules of perl-status, it attempts to
access this:
http://ourserver.com/perl-status?symdump
which doesn't work since the "test1" is missing, so I have taken to inserting
the "test1" into the URL manually. Not a showstopper, but annoying none the
less.
I may be missing some config to fix this, so this may not actually be a bug.
Thanks,
-Brian
---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org