01-23-2018 01:33 PM
we have this setup : portal --> facade --> WFS server
In portal, only wfs version 1.1.0 is available with "detect automatically".
If we select 1.1.0, everything works fine. If we choose "detect automatically", the request sent to the server is :
As you can see, acceptversions is 2.0.0, 1.1.0 that makes the service responding in version 2.0.0 which we don't want.
Is it possible de reverse the order (1.1.0, 2.0.0) or make sure that version 2.0.0 is not part of this parameter ?
Solved! Go to Solution.
01-25-2018 03:22 AM
You can create a service quirk for your WFS in Portal to exclude specific versions:
<serviceQuirk serviceType="WFS" urlPattern="yourWFSurl"> <excludeVersions> <add key="2.0.0" value="true"/> </excludeVersions> </serviceQuirk>
01-25-2018 06:04 AM
thanks for your answer.
I think we are on the right path.
The element "excludeVersions" is available starting with which version ?
With portal 2015 I get "Unrecognized element 'excludeVersions'."
Thanks for your help.
01-25-2018 06:18 AM - edited 01-25-2018 06:18 AM
As per the backlog, it should be available since 2015 EP04 and initial 2016 release. I tested it on 2016 EP04 where it worked fine.
It's currently documented only in the web.config file of Portal.