Hello,

since 7.13, my fetch script returns this error when fetching a webpage: "failure: ERROR parsing http: there was no content-length or transfer-encoding"
This fetch script calls a page from an ethernet relay board in the lan.

The device (ref: https://www.kmtronic.com/lan-ethernet-i ... board.html):


The routerOS code: The routerOS error returned: This behavior seems to have low visibility on the forums: looking around, I was only able to find one post from un9edsda here:
viewtopic.php?p=1048176#p1048176

It may be that the ethernet relay PCB doesn't revert a specific field, and I have no control over this, but until routerOS 7.13, this was not an issue: fetch seemed to be more flexible at accommodating this and returning the fetched content.
I confirm that freshly released 7.13.4 still display this error message.

What can be done to provide fetch the same level of flexibility it had until 7.12.1?

Thank you

Issue should be fixed in latest 7.14 beta versions

fantastic news, many thanks Normis!

Hi Normis,

I'm re-opening this:
I just updated to 7.14, but the error persists, although the error message is slightly different
Is there something I can provide you with in order to replicate?

Thanks

i'm with ROS 14.3 stable branch and this error persists.

I have a full range of scripts that push data to a prometheus pushgateway to audit quality of links and all of them just stop working on update.
Is there any solution to this?

Many thanks.

Also... i just realize that a sync script for an HA cluster just broke completly because of this.

This is so bad...

Hi @brunolabozzetta! Since this is a user forum, it's probably better if you contact MikroTik directly via email at "support@mikrotik.com" or open a support ticket using the link "https://help.mikrotik.com/servicedesk/servicedesk." //BR, Larsa.

This error is already identified and was supposed to be fixed in 7.14
But it’s still ongoing.
Ideally MikroTik can provide an ETA on resolution