Data Marshal Transit Flags and Headers
Accepted Flags
The Data Marshal Node network can respond to various flags that are injected via "query string params" and/or "response headers" that are attached to the Data Streams by their creators to trigger some custom behavior. These accepted flags are as follows:
dmf-nestedstream=1
[URL QueryString] Append this to your Data Stream URL
ipns://k51qzi5uqu5dkgpkqwl7gf60fu4clninr3fsge2i7x67kz0xfz5in5pu61epti?dmf-nestedstream=1
dmf-dnslink=1 & dmf-http=1
[URL QueryString] Append both these to your Data Stream URL
http://mydoamin.x/myfile.json?dmf-dnslink=1 &dmf-http=1
dmf-allow-http403=1
[URL QueryString] Append this to your Data Stream URL
https://api.itheumcloud-stg.com/datadexapi/bespoke/dynamicSecureDataStreamDemo?dmf-allow-http403=1
x-amz-meta-marshal-deep-fetch=1
[Server Response Header] Your Data Stream origin server can send this as response header
Send as regular HTTP response header
The same behavioir as the above "dmf-nestedstream=1" param, but is triggered by a server response header instead in he event you want to do this
Injected Headers
The Data Marshal Node network also injects some extra headers into each stream before it forwards it to the Data Stream origin server, which can then be used as needed. These injected headers are as follows:
itm-marshal-fwd-chainid
ED = MultiversX Devnet E1 = MultiversX Mainnet
itm-marshal-fwd-tokenid
The NFT token ID of any supported SFT or NFT collection. e.g. DATANFTFT-e0b917-ca (e.g. SFT) DNFTPHNAUT-f3f22a-02 (e.g. NFT)
Up to any 10 HTTP REQUEST HEADER and their values value
Example SDK Params:
...
fwdHeaderKeys: "authorization", fwdHeaderMapLookup: { "authorization": Bearer ${nativeAuthToken}
, }
...
Last updated