HttpCaller and Forefront TMG denied error

Hi @roberto

Could you share us the complete Log file?

Thanks,

Danilo

It may be an issue with the proxy configuration on your network. Depending on your FME version, proxy support may behave differently than your browser, notably if your proxy settings specify that the proxy should not be used for local addresses. This is a setting that FME may not always pick up, leading your request to go to the proxy rather than the intended server.

A workaround is to create a custom proxy map for your URL, here's an example for a URL that starts with http://my.local.server/...

This basically creates an exception in FME where you tell it to ignore the system proxy for all URLs starting with http://my.local.server

Hello,

here attached.

Thx

job_208067.txt

Hi David,

I tried to do it but it seems not solved.

Below the configuration (the url is a sample).

Have you tried the following configuration, based on the FME log you posted:

It may be (?) that you need to restart FME for this to take effect.

Hi,

yes I also tried that one and restarted. Without success.

Obviously, removing the firewall configuration in explorer, all works fine.

Roberto

And if you set "No proxy" in the FME options, does that work?

The same. It seems that windows proxy configuration overwrite the FME options.

That's strange. I recommend you forward this case to Safe support. It's also a good idea to link back to this thread so that they get the background info.

I'd be grateful if you could keep us informed on any relevant developements here.

Hi @roberto: Sorry to hear about your issues! What version and build of FME are you using?

There was an issue found where the Custom Proxy Map wasn't working in FME 2018.1. We recently fixed the issue and released it in the latest build of FME 2018.1.1.2 (b18586). If possible, try @david_r's recommendations again with the newest FME build and let us know if you have any luck.

We're still receiving this issue in FME 2018.1.1.2 (b18586). Can You confirm, that the bug has been fixed?

Hi @stezi, sorry to hear you are running into similar problems. It's hard to diagnose the problem to say for sure that the problem you observed is caused by the bug we fixed.