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: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
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:
Code:
:put [/tool fetch url="http://192.168.1.199/FF0100" as-value output=user]Code:
failure: ERROR parsing http: there was no content-length or transfer-encodingviewtopic.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
Statistics: Posted by eguun — Thu Feb 08, 2024 9:02 am