OCLOperators RestPost
No edit summary
Line 29: Line 29:


=== Rest checklist ===
=== Rest checklist ===
The url = the address of the remote service
'''The url''' = the address of the remote service


User & password = if provided will build up an Authentication request header of type basic ( == 'basic '+(user+':'+password).stringtobase64 )
'''User & password''' = if provided will build up an Authentication request header of type basic ( == 'basic '+(user+':'+password).stringtobase64 ) - when user == Bearer we will assume that the password is a bearer token that will be passed in an authentication header ( == Bearer tokenincleartext) (Note that some services are case sensistive on Bearer - we use the value you give in user un-altered).


Nesting with values = name of an existing Nesting (blue) in your ViewModel (green)
'''Nesting with values''' = name of an existing Nesting (blue) in your ViewModel (green)


In the Nesting you can add additional columns to control how data is sent to the remote service.
In the Nesting you can add additional columns to control how data is sent to the remote service.

Revision as of 13:23, 23 November 2019

Rest

RestGet, RestPost, RestPut, RestDelete and RestDownload are all operators on the selfVM variable only available in ViewModels.

These operators enables you to get or put information into external REST based services.

These operators works by adding a ViewModel Nesting/Class that has data and additional headers.

Rest explained: https://en.wikipedia.org/wiki/Representational_state_transfer

General rules and how to use headers in http and rest

Please read about the difference about request headers and content headers.

Nesting columns starting according to

For Content

  • STRINGCONTENT If the there's a column named then the request will be filled with StringContent(value as string)
  • FILENAME_xxx then the value if used as filename in a MultipartFormDataContent expecting a xxx column with byte data for the file content
  • HEADER_xxx then the value is added to the content as Headers.Add(xxx,value)
  • HEADERMINUS_xxx then the value is added to the content with the name underscores converted to dashes. I.e. as Headers.Add(xxx.Replace('_','-'),value)
  • HEADERMINUS_Content_Type ='application/x-www-form-urlencoded' will force the Post/Put into url-encoded-mode - all other columns are assumed to be strings that will be sent with a dictionary of name /values as FormUrlEncodedContent(theValuesForUrlEncoded)

The default content is MultipartFormDataContent, (values as dictionary) for example used in the Oauth2 implementation for server to server authentication

Also, note that content can only be sent in REST POST and PUT.

For the Request

  • DEFAULTREQUESTHEADER_xxx then the value is added to the request as client.DefaultRequestHeaders.Add(xxx,value)
  • DEFAULTREQUESTHEADERMINUS_xxx then the value is added to the request with the name underscores converted to dashes. I.e. as client.DefaultRequestHeaders.Add(xxx.Replace('_','-'),value)
  • FORCEREQUESTCONTENTTYPE can be used to force adding a Content Type header to GET request. Is it needed by some frameworks, but is actually an invalid request. It's implemented as adding a empty content and adding a header to that empty content. NOTE!! this should be avoided if possible!!

See further description here Rest Services In MDriven

Rest checklist

The url = the address of the remote service

User & password = if provided will build up an Authentication request header of type basic ( == 'basic '+(user+':'+password).stringtobase64 ) - when user == Bearer we will assume that the password is a bearer token that will be passed in an authentication header ( == Bearer tokenincleartext) (Note that some services are case sensistive on Bearer - we use the value you give in user un-altered).

Nesting with values = name of an existing Nesting (blue) in your ViewModel (green)

In the Nesting you can add additional columns to control how data is sent to the remote service.

It is the remote service that defines what you need to send - but you will quickly need to decide if the remote service expect content headers, request headers and payload in a specific format (one of MultiPartContent. StringContent or UrlEncodedContent). All values you send in the payload will be from the values in the Nesting - except any parameters you send in the url directly (Get and Delete operate this way).

There are 3 kind of values in the payload; Content headers (usually define what the content is), Request headers (usually very authentication information), and plain data. We separate between the 3 kinds of payload with a naming convention of the nesting columns name (begins with) - see above.

This page was edited 2 days ago on 03/26/2024. What links here