Allow reading response of fetch failing with HTTP error

RouterOS General
1

When a /tool fetch request returns an HTTP error (>= 400), the script terminates. I need to be able to read the response body. Perhaps some new option that doesn't terminate the script on HTTP errors?

2
3

Thanks, but I need the body, not just the headers.

4

output: user-with-headers - store downloaded data and headers in the data variable (variable limit is 64Kb (20Kb for downloaded data, 44Kb for headers))

5

That only works with a "successful" HTTP response. Otherwise the script still terminates, and I can't access the variable. It does print the request details to stdout, but even then the data field is empty.

6

from 2021, just search "fetch error" and:

7

I had seen that, but it's still not giving me the response body. I'm expecting a small JSON response.

Waiting the end of process for file testfetch.txt to be ready, max 20 seconds...
waiting... 1
waiting... 2
Done. Elapsed Seconds: 2

Result of Fetch:
****************************
  status: connecting

      status: failed
        code: 403   
  downloaded: 0KiB  

failure: Status 403, Forbidden (/tool/fetch; line 1)

****************************

Compared to using cURL:

HTTP/2 403
server: openresty
date: Thu, 27 Aug 2026 06:24:57 GMT
content-type: application/json
content-length: 58
vary: HX-Request, Accept-Language, Cookie, origin
allow: POST, OPTIONS
x-request-id: 38b151f4-01e5-4f69-b1f8-81119daffc5c
x-content-type-options: nosniff
referrer-policy: same-origin
cross-origin-opener-policy: same-origin
x-frame-options: SAMEORIGIN
content-language: en

{"detail":"Authentication credentials were not provided."}