Allow FME Server to use both leading and trailing wildcard exceptions in FME Server. Eg. *.domain.* within the Web UI.
Released
Allow FME Server to use Wildcard Exceptions for Proxy Settings
This post is closed to further activity.
It may be an old question, an answered question, an implemented idea, or a notification-only post.
Please check post dates before relying on any information in a question or answer.
For follow-up or related questions, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.
It may be an old question, an answered question, an implemented idea, or a notification-only post.
Please check post dates before relying on any information in a question or answer.
For follow-up or related questions, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.
+2- Contributor
With the increased usage of web services within our organisation across many servers behind the proxy this change will make listing out the excluded servers an awful lot simpler.
This is important functionality for most of our enterprise and government clients, of which many are behind centrally managed proxy servers. Since the local servers are unknown to the proxy server, wildcards are extremely helpful in routing network access.
+14- Safer
Update: This is currently in progress and will be available in FME Server 2020.1 betas – please use Build 20530 or newer from safe.com/beta.
+10- Contributor
Hi @rylanatsafe,
Good news Rylan, I'm looking forward to this.
Kind regards,
Krien Guijt
+14- Safer
This has been released with FME Server 2020.1 – available now!
Login to the community
No account yet? Create an account
An FME Account is required to contribute
LoginEnter your E-mail address. We'll send you an e-mail with instructions to reset your password.