How to send X-CSRF:x with Create HTTP REST Client?

[Relativity1]

Hello LV Gurus,

I am creating a simple GUI to control a web (specifically RESTful web server) based DLI Web Power Switch Pro

I have three problems:

1. What is the "Base URL" Is it just the IP + port (e.g. http://192.168.0.100:80) or the whole URI including the path to the web server (e.g. http://192.168.0.100/restapi/relay/outlets/0/state/)
2. Where and how do I insert the cross-site forgery ignore in the header (e.g. X-CSRF:x) with your REST API? The Default Header list does not include X-CSRF.
3. Do you support Basic and/or Digest authentication? I get "Unauthorized" error messages using your PUT (or GET) methods returned in the Status String.

I then proceeded to create a version of this GUI using cURL (via the System Exec node) to enable switch outlet 1 using "digest" authentication and it works:

curl --digest -u admin:1234 -X PUT -H "X-CSRF: x" --data "value=true" "http://192.168.0.100/restapi/relay/outlets/0/state/"

FYI: This is DLI guideline for using RESTful HTTP on their power switches

Thanks in advance guys. You do wonders for us LabVIEW cogs!

Relativity1

Edited May 21, 2020 by Relativity1
images in the wrong places

[Jim Kring]

Hi There! Glad you like the JKI HTTP REST client.

Quote

1) What is the "Base URL" Is it just the IP + port (e.g. http://192.168.0.100:80) or the whole URI including the path to the web server (e.g. http://192.168.0.100/restapi/relay/outlets/0/state/)

For the base URI, I would use:

http://192.168.0.100/restapi

and then for the path when you call GET or POST, use:

/relay/outlets/0/state/

 

Quote

2) Where and how do I insert the cross-site forgery ignore in the header (e.g. X-CSRF:x) with your REST API? The Default Header list does not include X-CSRF.

Here's how you could add the X-CSRF header. Note that you can type (or copy-paste) new items into the drop-down selector for the header -- it works like a string control, but with some pre-defined options to make life easier for common headers. 

Quote

Do you support Basic and/or Digest authentication? I get "Unauthorized" error messages using your PUT (or GET) methods returned in the Status String.

The JKI HTTP REST Client passes the username and password into the HTTP VI used by built-in HTTP Open Handle.vi, which I believe doesn't support digest authentication.

Under the hood...

Digest authentication is something that could be added -- here's the specification and here's a demo server, if you're interested in trying.