Skip to main content
Question

HTTPCaller transferred a partial file


messagemauri
Contributor
Forum|alt.badge.img+6

Hello,

I’ve had a workbench running on FME Server and FME Desktop 2022.2 perfectly fine through the last 2 years. Suddenly, it’s throwing an error HTTP Transfer error: Transferred a partial file. 

I tested it with FME Server and FME Desktop 2022.2 and get the same error. When I access the url through a browser, it perfectly downloads the zip file. But the HTTPCaller fails. 

Request Url: https://static.aer.ca/prd/data/wells/PLA_RTF_SHP.zip

Any insights would be greatly appreciated.

Thank you.

 

Sample below for testing purposes, attempting to download the file in my local.

HTTPCaller settings: 

 

Error:

 

4 replies

ctredinnick
Supporter
Forum|alt.badge.img+18
  • Supporter
  • January 9, 2025

The download works for me in 2022.2, with the same default settings on a HTTP Caller.

Debugging an error happening in an HTTPCaller can often be made clearer by temporarily changing the logging settings. Option → Translation → Log Message Filter → Debug, to see the full details on what it’s doing.


redgeographics
Celebrity
Forum|alt.badge.img+49

It’s a 33 Mb file, which downloaded in a few seconds for me, so I doubt it’s a timeout error. Can you try another url (like e.g. www.google.com) and see if the same happens? If you’re on a corporate network or VPN it may be that http access is only granted for browsers, not other applications.


virtualcitymatt
Celebrity
Forum|alt.badge.img+35

Yeah I also tried with FME FME 2022 and had no issues - I second the suggestion by ​@ctredinnick to turn on debug logging. HTTP Requests are one of the few places in FME where debug logging is really helpful. 


messagemauri
Contributor
Forum|alt.badge.img+6
  • Author
  • Contributor
  • January 10, 2025

Thank you guys for your valuable input. I tried it again today, (the day after the error) and enabled the FME Log Debugger. However, everything works fine today with no errors. Unfortunately I couldn’t make use of the debugger to pin point the cause, but I will keep this in mind for next time. As for ​@redgeographics , I tried the HTTPCaller with www.google.com and it worked fine. Could have been a network thing that was temporarily causing the error. Will take note of this for next time as well. Thanks again. 


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings