Community discussions

 
Lukasz032
just joined
Topic Author
Posts: 4
Joined: Tue Apr 29, 2014 4:31 pm

Feature request: Make /tool fetch compatible with HTTP/HTTPS POST/PUT/PATCH methods

Wed May 18, 2016 12:08 am

At present, the only thing I can do using /tool fetch command is to make a GET call over HTTP/HTTPS or transfer files using FTP/TFTP. This tool is lacking a proper support for POST, PUT and PATCH methods over HTTP/HTTPS, which is problematic mainly because of it's impossible to do things the right way, like i.e. sending logfiles over HTTP PUT to a remote server.

There is also a more reasonable reason to implement this feature. As you can read, CloudFlare has deprecated their "normal" API calls used to set parameters like IP address on their hosted (D)DNS service. After November 9, all the RBs will be unable to update their records, which will affect dynamic IP users running webservers over their links. The only way to update the records will be to issue a HTTPS PUT or PATCH call with the new address, not a GET one.

Screw all the REST thing, but in my opinion, this will be a very desirable feature and it would simplify some scripting on RBs.
 
Tinuva
just joined
Posts: 6
Joined: Fri May 01, 2009 11:21 am

Re: Feature request: Make /tool fetch compatible with HTTP/HTTPS POST/PUT/PATCH methods

Fri Nov 04, 2016 12:49 pm

Also would like this.

Sadly no more DynDNS with CloudFlare :(
 
savage
Forum Guru
Forum Guru
Posts: 1168
Joined: Mon Oct 18, 2004 12:07 am
Location: Cape Town, South Africa
Contact:

Re: Feature request: Make /tool fetch compatible with HTTP/HTTPS POST/PUT/PATCH methods

Fri Nov 04, 2016 2:36 pm

dst-path=/dev/null would also be very nice considering we're talking about fetch...

There's very few (none?) methods to test speeds from an ACTUAL mikrotik, that is compatible with the rest of the world... A simple HTTP download, bypassing the slow storage disks, may be a good start.

Asking for something like netperf in MT would more than likely be too much :lol:
Regards,
Chris
 
User avatar
boen_robot
Forum Guru
Forum Guru
Posts: 2369
Joined: Thu Aug 31, 2006 4:43 pm
Location: europe://Bulgaria/Plovdiv

Re: Feature request: Make /tool fetch compatible with HTTP/HTTPS POST/PUT/PATCH methods

Sat Nov 05, 2016 1:49 pm

dst-path=/dev/null would also be very nice considering we're talking about fetch...
That one is already doable with 'keep-result=no'.
PEAR2_Net_RouterOS(1.0.0b6) - My API client in PHP
(Rate my posts? If you want... no pressure...)
 
Lukasz032
just joined
Topic Author
Posts: 4
Joined: Tue Apr 29, 2014 4:31 pm

Re: Feature request: Make /tool fetch compatible with HTTP/HTTPS POST/PUT/PATCH methods

Wed Sep 13, 2017 4:53 am

For now, I've developed a substitute, temporary solution: change the update URL to this: http://ldev.pl/cloudflare_updater.php with the same parameters as in the previous API. It just repacks the request payload into a "new" format and sends it to Cloudflare. Besides, it isn't an ideal solution since it relies on an external server, but for now it's working :)
 
User avatar
Paxy
just joined
Posts: 21
Joined: Mon May 26, 2008 8:28 pm

Re: Feature request: Make /tool fetch compatible with HTTP/HTTPS POST/PUT/PATCH methods

Wed Sep 20, 2017 6:27 pm

Custom headers for /tool fetch too.
 
User avatar
Cha0s
Forum Veteran
Forum Veteran
Posts: 722
Joined: Tue Oct 11, 2005 4:53 pm

Re: Feature request: Make /tool fetch compatible with HTTP/HTTPS POST/PUT/PATCH methods

Fri Sep 22, 2017 11:36 am

Or just replace fetch with cURL and almost everyone will be happier :)
 
eriitguy
Member Candidate
Member Candidate
Posts: 197
Joined: Thu Jan 26, 2017 1:16 pm

Re: Feature request: Make /tool fetch compatible with HTTP/HTTPS POST/PUT/PATCH methods

Mon Sep 25, 2017 4:43 pm

Hello!

May be related to the compatibility: tool fetch - 2xx HTTP response codes

Thank you!

Who is online

Users browsing this forum: No registered users and 5 guests