Community discussions

MikroTik App
 
eguun
Frequent Visitor
Frequent Visitor
Topic Author
Posts: 82
Joined: Fri Apr 10, 2020 10:18 pm

fetch error since 7.13: "failure: ERROR parsing http: there was no content-length or transfer-encoding"

Thu Feb 08, 2024 9:02 am

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):
Image

The routerOS code:
:put [/tool fetch url="http://192.168.1.199/FF0100" as-value output=user]
The routerOS error returned:
failure: ERROR parsing http: there was no content-length or transfer-encoding
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
 
User avatar
normis
MikroTik Support
MikroTik Support
Posts: 26363
Joined: Fri May 28, 2004 11:04 am
Location: Riga, Latvia

Re: fetch error since 7.13: "failure: ERROR parsing http: there was no content-length or transfer-encoding"

Thu Feb 08, 2024 9:28 am

Issue should be fixed in latest 7.14 beta versions
 
eguun
Frequent Visitor
Frequent Visitor
Topic Author
Posts: 82
Joined: Fri Apr 10, 2020 10:18 pm

Re: fetch error since 7.13: "failure: ERROR parsing http: there was no content-length or transfer-encoding"

Thu Feb 08, 2024 9:37 am

fantastic news, many thanks Normis!
 
eguun
Frequent Visitor
Frequent Visitor
Topic Author
Posts: 82
Joined: Fri Apr 10, 2020 10:18 pm

Re: fetch error since 7.13: "failure: ERROR parsing http: there was no content-length or transfer-encoding"

Fri Mar 01, 2024 9:48 am

Hi Normis,

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

Thanks

Who is online

Users browsing this forum: astronomicz, Bing [Bot], citramasit, Gomo, ivicask, NetworqAndy and 64 guests