Hi,
 
 
I'm guessing that the WFS reader has a hard time separating the parameters to the proxy (the outbound URL, in this case) and the necessary parameters that it has to juggle for the WFS features. I would say this is almost to be expected.
 
 
If possible, try to reconfigure your proxy so that you have a specific URL that redirectes, e.g.
 
 
https://example.com/WFSServerProxy.ashx?.... 
 
routes to 
 
 
https://fmeserver.local.com/MapServer/WFSServer?... 
 
leaving all the parameters unchanged.
 
 
The clue here is to avoid passing the outbound URL as a parameter to your proxy, but rather let the proxy rewrite the URL based on a configuration rule.
 
 
Hope this makes sense :-)
 
 
David
                
     
                                    
            Dear David
 
Thank you for the replay.
 
That would be a solution to reconfigure the proxy. But it is a general proxy for different services, it would be nice not to change this setting. 
 
 
What I suppose is that the reader just attach the parameters after the url?
 
 
On the other hand, is there a direct way to communicate with a secure token WFS from an ArcGIS Server without proxy? Is it possible to use this with a reader from FME?
 
Cheers
 
Sascha
 
 
 
 
                
     
                                    
            Hi
 
Has anyone managed to resolve this since the original post?
 
Cheers
 
ACM