[IMP] server: rename xmlrpc* related parameters

The 'xmlrpc'-based configuration parameters have been a misnomer since
the introduction of the generic HTTP service, years ago.

Hide these options from the server parameters, and replace them with
more appropriate 'http' ones:

 --xmlrpc-interface -> --http-interface
 --xmlrpc-port      -> --http-port
 --no-xmlrpc        -> --no-http

The config entries for these have been adapted as well.

The old parameter names are still silently supported in both
command-line arguments and config files. However they are
stored with the new names in the `tools.config` dict,
and when saving config files (with the -s option).

Also clarified and cleaned up the descriptions of the HTTP/WEB server
parameters.

And finally, added a short version `-p`, for the `--http-port` option.
Credits to @dreispt for this (via #19518)

Closes #19518
Closes #19778

2 files changed, 6 insertions, 6 deletions

diff --git a/doc/reference/cmdline.rst b/doc/reference/cmdline.rst
index 37b0e9db646..d35868a718f 100644
--- a/doc/reference/cmdline.rst
+++ b/doc/reference/cmdline.rst
@@ -177,7 +177,7 @@ database
 built-in HTTP
 -------------
 
-.. option:: --no-xmlrpc
+.. option:: --no-http
 
     do not start the HTTP or long-polling workers (may still start cron
     workers)
@@ -185,12 +185,12 @@ built-in HTTP
     .. warning:: has no effect if :option:`--test-enable` is set, as tests
                  require an accessible HTTP server
 
-.. option:: --xmlrpc-interface <interface>
+.. option:: --http-interface <interface>
 
     TCP/IP address on which the HTTP server listens, defaults to ``0.0.0.0``
     (all addresses)
 
-.. option:: --xmlrpc-port <port>
+.. option:: --http-port <port>
 
     Port on which the HTTP server listens, defaults to 8069.
 
@@ -375,7 +375,7 @@ and other ``-`` are replaced by ``_`` e.g. :option:`--db-template` becomes
 Some conversions don't match the pattern:
 
 * :option:`--db-filter` becomes ``dbfilter``
-* :option:`--no-xmlrpc` corresponds to the ``xmlrpc`` boolean
+* :option:`--no-http` corresponds to the ``http_enable`` boolean
 * logging presets (all options starting with ``--log-`` except for
   :option:`--log-handler` and :option:`--log-db`) just add content to
   ``log_handler``, use that directly in the configuration file
diff --git a/doc/setup/deploy.rst b/doc/setup/deploy.rst
index 983a2318117..9879117b607 100644
--- a/doc/setup/deploy.rst
+++ b/doc/setup/deploy.rst
@@ -211,7 +211,7 @@ the client will not connect to it.
 
 Instead you must have a proxy redirecting requests whose URL starts with
 ``/longpolling/`` to the longpolling port. Other request should be proxied to
-the :option:`normal HTTP port <odoo-bin --xmlrpc-port>`
+the :option:`normal HTTP port <odoo-bin --http-port>`
 
 .. warning:: The livechat worker requires the ``psycogreen`` Python module,
              which is not always included with all installation packages.
@@ -357,7 +357,7 @@ To run cron jobs for an Odoo deployment as a WSGI application requires
   :option:`odoo-bin -d`)
 * which should not be exposed to the network. To ensure cron runners are not
   network-accessible, it is possible to disable the built-in HTTP server
-  entirely with :option:`odoo-bin --no-xmlrpc` or setting ``xmlrpc = False``
+  entirely with :option:`odoo-bin --no-http` or setting ``http_enable = False``
   in the configuration file
 
 LiveChat