Revision bfcd1652
b/doc/rapi.rst | ||
---|---|---|
75 | 75 |
by using the standard HTTP basic access authentication. This means that |
76 | 76 |
for accessing the protected URL ``https://cluster.example.com/resource``, |
77 | 77 |
the address ``https://username:password@cluster.example.com/resource`` should |
78 |
be used instead. |
|
78 |
be used instead. Alternatively, the appropriate parameter of your HTTP client |
|
79 |
(such as ``-u`` for ``curl``) can be used. |
|
79 | 80 |
|
80 | 81 |
.. [#pwhash] Using the MD5 hash of username, realm and password is |
81 | 82 |
described in :rfc:`2617` ("HTTP Authentication"), sections 3.2.2.2 |
... | ... | |
279 | 280 |
$ curl https://%CLUSTERNAME%:5080/2/info |
280 | 281 |
|
281 | 282 |
Note: with ``curl``, the request method (GET, POST, PUT) can be specified |
282 |
using the ``-X`` command line option. |
|
283 |
using the ``-X`` command line option, and the username/password can be |
|
284 |
specified with the ``-u`` option. In case of POST requests with a body, the |
|
285 |
Content-Type can be set to JSON (as per the Protocol_ section) using the |
|
286 |
parameter ``-H "Content-Type: application/json"``. |
|
283 | 287 |
|
284 | 288 |
Python |
285 | 289 |
++++++ |
Also available in: Unified diff