From a7d2c8e6ad9d3c8af868349537318172ec4f2695 Mon Sep 17 00:00:00 2001 From: steve-chavez Date: Mon, 18 Dec 2023 23:58:17 -0500 Subject: [PATCH] docs: soap how-to is outdated `*/*` can now be handled with media type handlers --- docs/how-tos/create-soap-endpoint.rst | 21 +-------------------- 1 file changed, 1 insertion(+), 20 deletions(-) diff --git a/docs/how-tos/create-soap-endpoint.rst b/docs/how-tos/create-soap-endpoint.rst index 8114d7cec..1e481d37a 100644 --- a/docs/how-tos/create-soap-endpoint.rst +++ b/docs/how-tos/create-soap-endpoint.rst @@ -77,25 +77,6 @@ and should roughly look like: -Unfortunately the ``Accept: text/xml`` header is currently mandatory concerning PostgREST, otherwise it will respond -with a ``Content-Type: application/json`` header and enclose the response with quotes. -(You can check the returned headers by adding ``-v`` to the curl call.) - -If your SOAP clients do not send the ``Accept: text/xml`` header, you can fix that in your nginx reverse proxy -by adding something like ... - -.. code-block:: nginx - - set $accept $http_accept; - if ($contentType ~ "^text/xml($|;)") { - set $accept "text/xml"; - } - proxy_set_header Accept $accept; - -to your ``location`` nginx configuration. -(The given example sets the ``Accept`` header for each request of Content-Type ``text/xml``.) - - A more elaborate example ------------------------ @@ -211,7 +192,7 @@ References For more information concerning PostgREST, cf. - :ref:`s_proc_single_unnamed` -- :ref:`custom_media`. See :ref:`any_handler`, if you need to support an ``application/soap+xml`` media type. +- :ref:`custom_media`. See :ref:`any_handler`, if you need to support an ``application/soap+xml`` media type or if you want to respond with XML without sending a media type. - :ref:`Nginx reverse proxy ` For SOAP reference, visit