Hi @edhere

Did you try to extract this using the Reader HTML Table or the transformer HTML Extractor?

Thanks,

Danilo

Thanks for your fast response.

I still wonder why the HTTPCaller fails...?

I am getting exactly the same response through HttpCaller(GET). The URL is:

https://apilesv3.utv.atlas.vegvesen.no/posisjon?nord=7733937.931&ost=656006.776&maks_avstand=25&maks_antall=10&srid=6173

And it works perfectly through Postman and Chrome netbrowser from the same machine running FME(R) 2019.2.0.0 (20191105 - Build 19801 - WIN64)

What i do not really understand is why it worked before (no settings changed on HttpCaller) but not now. Have you experienced this HttpCallers behavior before?

After closing the workspace and starting it again, it works!? why? Now it works as expected, but it will be nice to hear from you about the issue. Our client will use this in the future and i would like to be sure that, as long as the API works and internet is available, the HttpCaller is able to GET something :)

Hi @tono,

Thanks for your question! I realize this thread is a bit older than I would usually like to carry a discussion on, but it looks like there's an issue with a similar description (potentially FMEENGINE-30279 for tracking).

When the HTTPCaller failed, did you run the workspace with the HTTP call twice in succession? And if so, is it failing on the second run?

What I've gleaned from the issue is that it's a server side problem with the service that you're trying to access. A potential workaround is to use the Decelerator before the httpcaller. Let me know if that works for you, and if it really is the same issue, thanks!