# For the URL https://kea.example.org forward the
# requests to http://127.0.0.1:8000.
- # Since kea-shell doesn't currently support URLs with paths we
- # use location /
+ # kea-shell defaults to / but --path can be used to set another value
+ # for instance kea-shell --path kea which will matches location /kea
location / {
proxy_pass http://127.0.0.1:8000;
}
<title>Shell Usage</title>
<para><command>kea-shell</command> is run as follows:
<screen>
-kea-shell [--host hostname] [--port number] [--timeout seconds] [--service service-name] [command]
+kea-shell [--host hostname] [--port number] [--path path] [--timeout seconds] [--service service-name] [command]
</screen>
where:
</para>
</simpara>
</listitem>
+ <listitem>
+ <simpara>
+ <command>--path <replaceable>path</replaceable></command> specifies
+ the path in the URL to connect to. If not specified,
+ empty path is used. As CA listens at the empty path
+ this parameter is useful only with a reverse proxy.
+ </simpara>
+ </listitem>
+
<listitem>
<simpara>
<command>--timeout <replaceable>seconds</replaceable></command> specifies the
</screen>
</para>
+ <para>When a reverse proxy is used to de-multiplex requests to different
+ servers the default empty path in the URL is not enough so the
+ <command> --path </command> parameter should be used. For instance
+ if requests to the "/kea" path are forwarded to the CA this can be used:
+<screen>
+$ <userinput>kea-shell --host 192.0.2.1 --port 8001 --path kea ...</userinput>
+</screen>
+ </para>
+
<para>Kea Shell requires Python to to be installed on the system. It was tested with
Python 2.7 and various versions
of Python 3, up to 3.5. Since not every Kea deployment uses this feature and there are