Skip to main content
  • EN

Hi,

I have HTTPCaller in my workspace, and two urls to retrieve from server which requires NTLM authorization.

Now, the retrieval of second url always fails, and I see in logs that libcurl doesn't send NTLM auth info on second call. I tried to enable Save Cookies, but it didn't help - server asks for auth on each request.

FME(R) 2015.1.3.2 (20160108 - Build 15575 - WIN32)

Any suggestion other than putting httpcaller in separate workspace and run it with workspacerunner? that time it will create separate instances of HTTPCaller for each url.

have you tried a second httpcaller parallel to the first one?

have you tried a second httpcaller parallel to the first one?

Yes I did and it worked. But I will have different number of URLs each time, so this solution is not acceptable.

 

Also, I tried to download via FeatureReader, and it seems like FR works fine each time, but the XML file behind URL could not be parsed that way due to its tricky structure.

 

I think this is a good question to send to either your local reseller or to the Safe Software support team (safe.com/support) - it sounds like a bug that needs fixing.

 

 

For a workaround I thought the FeatureReader sounded like the best chance of a solution. You must be able to have the XML returned whole, and not flattened. Maybe needs an xfmap. But you may be quicker to use a WorkspaceRunner as you suggest. When you contact the support team about the issue, ask them if they can think of a good workaround.

 

 

Hope this helps!

 

 

OK, use the FeatureReader, set the format to Text File and enter the URL in the dataset. Under parameters set "Read Whole File at Once" to Yes. Click the authentication option and enter your authentication settings.

That way you'll be able to read the entire XML, just as if you'd fetched it directly with the HTTPCaller.

OK, use the FeatureReader, set the format to Text File and enter the URL in the dataset. Under parameters set "Read Whole File at Once" to Yes. Click the authentication option and enter your authentication settings.

That way you'll be able to read the entire XML, just as if you'd fetched it directly with the HTTPCaller.

I have no authentication option in FeatureReader when Format is set to Text File and URL is given in attribute. When I enter URL directly or if I specify url in Dataset field like 'http://@Value(MY_URL)' the authentication option is available. That way it works.

 

 

Thanks, Mark!

 

 

 

But it looks like if I specify URL for text file in FeatureReader as

'http://@Value(MY_URL)' the authentication details are not saved in FeatureReader

Correction: Authentication details are saved in FeatureReader, but when you open it next time, all fields are blank.

I have no authentication option in FeatureReader when Format is set to Text File and URL is given in attribute. When I enter URL directly or if I specify url in Dataset field like 'http://@Value(MY_URL)' the authentication option is available. That way it works.

 

 

Thanks, Mark!

 

 

 

Yikes! I'll file that as a problem with our developers.

 

 

But it looks like if I specify URL for text file in FeatureReader as

'http://@Value(MY_URL)' the authentication details are not saved in FeatureReader

Correction: Authentication details are saved in FeatureReader, but when you open it next time, all fields are blank.

OK. Well that problem at least is fixed in FME2016. If you can upgrade to that version, you will be good to go. I don't know that I can see a workaround for that in 2015.

 

Our developer can't replicate the original problem in FME2017, so thinks it has been fixed by one of the many updates we've applied to that transformer. Can you try it out in a beta version? Either FME 2017 or maybe even 2016.1.2. That way we'd at least know if it's fixed, even if you can't use a beta for production work.

See http://www.safe.com/support/support-resources/fme-downloads/beta/ for the beta downloads

Our developer can't replicate the original problem in FME2017, so thinks it has been fixed by one of the many updates we've applied to that transformer. Can you try it out in a beta version? Either FME 2017 or maybe even 2016.1.2. That way we'd at least know if it's fixed, even if you can't use a beta for production work.

See http://www.safe.com/support/support-resources/fme-downloads/beta/ for the beta downloads

I will try it.

 

 

Our developer can't replicate the original problem in FME2017, so thinks it has been fixed by one of the many updates we've applied to that transformer. Can you try it out in a beta version? Either FME 2017 or maybe even 2016.1.2. That way we'd at least know if it's fixed, even if you can't use a beta for production work.

See http://www.safe.com/support/support-resources/fme-downloads/beta/ for the beta downloads

Mark, it works in 2016.1.2 and even 2016.1. Thanks for your help!

 

 

Reply


Community Stats

30,122
Posts
114,333
Replies
37,751
Members
Terms & ConditionsCookie settings
A product of
Safe Software respectfully acknowledges that we live, learn and work on the traditional and unceded territories of the Kwantlen, Katzie, and Semiahmoo First Nations.