Some services require a hash been sent as a custom field on the HTTP header to perform secure authentication.

With curl it is easily doable with the -H flag. Would like to have something similar supported on Mikrotik

/tool fetch http-method=put http-content-type="application/json" http-data=("{\"name\":\"".$name."\",\"data\":\"".$data."\"}") url=("www.xyz.com/api/record")

to

/tool fetch http-method=put http-content-type="application/json" http-header="Authorization: xxxxxx" http-data=("{\"name\":\"".$name."\",\"data\":\"".$data."\"}") url=("www.xyz.com/api/record")

Thanks

Pat

Good day
me too
I need it so much !

Hello, I agree with this petition.

Hi, I think there are some features that would be very useful in fetch support, if it is possible to include them...


- Http-Header
- Keyed-hash message authentication code in these request. (HMAC-MD5 or HMAC-SHA1)
- Base64. Like SCEP do.

IMHO, much appreciated!

Bumping this request

We are also waiting for the exteremely useful ability to provide with custom HTTP headers on FETCH requests.

Best regards.
AV

Please, need this for better Slack messaging - would like to send via POST/JSON, URL encoding using RouterOS scripting is hell...
https://github.com/massimo-filippi/mikr ... -slack.rsc

This feature would be handy in terms of backup to owncloud/nextcloud.

See: Upload to “File Drop” using curl from command line

One more for this. Please, please, please allow custom header fields.

I would prefer to do this directly from the router than from a script on one of the servers behind it.

Already possible

/tool fetch http-header-field=

Thanks a lot for implementing this feature!!!!