Perlbal::Manual::WebServer(3pm) | User Contributed Perl Documentation | Perlbal::Manual::WebServer(3pm) |
Perlbal::Manual::WebServer - Configuring Perlbal as a Web Server
Perlbal 1.78.
How to configure a Perlbal Web Server service.
Please read Perlbal::Manual::Configuration first for a better explanation on how to configure Perlbal. This document will make much more sense after reading that.
By default, perlbal looks for a configuration file at /etc/perlbal/perlbal.conf.
You can also point perlbal at a different configuration file with the -c flag.
$ perlbal -c /home/user/perlbal.conf
Here's a very simple example where we configure a simple web server that serves an index file under /tmp
CREATE SERVICE perlbal_test SET role = web_server SET listen = 0.0.0.0:80 SET docroot = /tmp ENABLE perlbal_test
The first line creates a service called "perlbal_test". The last line enables that service.
The three parameters state - in order - that the service is a web server, that it listens on all addresses on port 80, and that its document root is "/tmp".
You can set parameters via commands of either forms:
SET <service-name> <param> = <value> SET <param> = <value>
Default if false.
Useful for web apps which have dozens/hundreds of tiny css/js files, and don't trust browsers/etc to do pipelining.
Decreases overall round-trip latency a bunch, but requires app to be modified to support it. See t/17-concat.t test for details.
Default is false.
Default is true.
Default is false.
Default is false.
Default is index.html.
Default is 0, which means there is no limit.
Default is 0.
Perlbal by default adds a header to all replies (such as the web_server role). By setting this default to "off", you can prevent Perlbal from identifying itself.
Default is "on".
Perlbal::Manual::Configuration, Perlbal::Manual::Management.
2021-01-07 | perl v5.32.0 |