Peut accéder au service WCF via le navigateur, mais pas via un GET dans PowerShell

Question

J'ai un service WCF qui fonctionne bien via le navigateur, il renvoie le résultat que je m'attends. Maintenant, lorsque vous essayez d'y accéder via PowerShell, je reçois cette erreur

Invoke-WebRequest : The underlying connection was closed: An unexpected error occurred on a send. 

Je suis d'hébergement ceci sur IIS comme une application qui pointe à l'emplacement du service sur mon système, appelé « ValidationServiceApp » Je peux y accéder via: "https://myPc/ValidationServiceApp/RemoteService.svc/validationresult/"

Voici le code PowerShell:

[Net.ServicePointManager]::ServerCertificateValidationCallback = {$true} #handle unsigned certs as its on my local machine on IIS 
$testurl = "https://myPc/ValidationServiceApp/RemoteService.svc/validationresult/" 
$result = Invoke-WebRequest -Method GET -Uri $testurl 
Write-Host $result 

le service VS:

IRemoteService.cs

[OperationContract] 
     [WebInvoke(Method = "GET", ResponseFormat = WebMessageFormat.Json, 
      BodyStyle = WebMessageBodyStyle.Wrapped, 
      UriTemplate = "ValidationResult/")] 
     bool ValidationResult(); 

RemoteService.svc.cs

public bool ValidationResult() 
{ 
    return true; 
    //throw new NotImplementedException(); 
} 

web.config

<?xml version="1.0"?> 
<configuration> 

    <appSettings> 
    <add key="aspnet:UseTaskFriendlySynchronizationContext" value="true"/> 
    </appSettings> 
    <system.web> 
    <compilation debug="true" targetFramework="4.6"/> 
    <httpRuntime targetFramework="4.6"/> 
    <httpModules> 
     <add name="ApplicationInsightsWebTracking" type="Microsoft.ApplicationInsights.Web.ApplicationInsightsHttpModule, Microsoft.AI.Web"/> 
    </httpModules> 
    </system.web> 
    <system.serviceModel> 
    <bindings> 
     <webHttpBinding>  
     <binding name="webHttpTransportSecurity"> 
      <security mode="Transport"> 
      <transport clientCredentialType="None" proxyCredentialType="None" /> 
      </security> 
     </binding> 
     </webHttpBinding> 
    </bindings> 
    <services> 
     <service name="RemoteService.RemoteService" behaviorConfiguration="ServiceBehaviour">   
     <endpoint address ="" 
        binding="webHttpBinding" 
        contract="RemoteService.IRemoteService" 
        bindingConfiguration="webHttpTransportSecurity" 
        behaviorConfiguration="web" /> 

     <endpoint address="mex" 
        binding="mexHttpsBinding" 
        contract="IMetadataExchange" /> 
     </service> 
    </services> 
    <behaviors> 
     <serviceBehaviors> 
     <behavior name="ServiceBehaviour"> 
      <!-- To avoid disclosing metadata information, set the values below to false before deployment --> 
      <serviceMetadata httpGetEnabled="false" httpsGetEnabled="true"/> 
      <!-- To receive exception details in faults for debugging purposes, set the value below to true. Set to false before deployment to avoid disclosing exception information --> 
      <serviceDebug includeExceptionDetailInFaults="false"/> 

     </behavior> 
     </serviceBehaviors> 
     <endpointBehaviors> 
     <behavior name="web"> 
      <webHttp/> 
     </behavior> 
     </endpointBehaviors> 
    </behaviors> 
    <protocolMapping>  
     <add binding="webHttpBinding" scheme="https"/> 
    </protocolMapping>  
    <serviceHostingEnvironment aspNetCompatibilityEnabled="true" multipleSiteBindingsEnabled="true"/> 
    </system.serviceModel> 
    <system.webServer> 
    <modules runAllManagedModulesForAllRequests="true"> 
     <remove name="ApplicationInsightsWebTracking"/> 
     <add name="ApplicationInsightsWebTracking" type="Microsoft.ApplicationInsights.Web.ApplicationInsightsHttpModule, Microsoft.AI.Web" 
     preCondition="managedHandler"/> 
    </modules> 
    <!-- 
     To browse web app root directory during debugging, set the value below to true. 
     Set to false before deployment to avoid disclosing web app folder information. 
     --> 
    <directoryBrowse enabled="true"/> 
    <validation validateIntegratedModeConfiguration="false"/> 
    </system.webServer> 

</configuration> 

Answer 1

Envisager d'utiliser l'applet de commande New-WebServiceProxy lorsque vous travaillez avec un webservice WCF dans PowerShell.

$proxy= New-WebServiceProxy -Uri "https://myPc/ValidationServiceApp/RemoteService.svc" 
# retrieve available methods: 
$proxy | Get-Member