The provided URI scheme https is invalid expected http Parameter name via

Question

I am trying to make a WCF service over basicHttpBinding to be used over https  Here s my web config    lt  -- language  xml -- gt   lt service behaviorConfiguration  MyServices PingResultServiceBehavior           name  MyServices PingResultService  gt       lt endpoint address                   binding  basicHttpBinding                 bindingConfiguration  defaultBasicHttpBinding                contract  MyServices IPingResultService  gt           lt identity gt               lt dns value  localhost    gt           lt  identity gt       lt  endpoint gt       lt endpoint address  mex                 binding  mexHttpBinding                 contract  IMetadataExchange    gt   lt  service gt         lt bindings gt     lt basicHttpBinding gt       lt binding name  defaultBasicHttpBinding  gt         lt security mode  Transport  gt           lt transport clientCredentialType  None   gt         lt  security gt       lt  binding gt     lt  basicHttpBinding gt   lt  bindings gt       lt behaviors gt     lt serviceBehaviors gt       lt behavior name  MyServices UpdateServiceBehavior  gt         lt serviceMetadata httpsGetEnabled  true    gt         lt serviceDebug includeExceptionDetailInFaults  true    gt       lt  behavior gt     lt  serviceBehaviors gt   lt  behaviors gt    I am connecting using WCFStorm which is able to retrieve all the meta data properly  but when I call the actual method I get      The provided URI scheme  https  is invalid  expected  http   Parameter   name  via

User · Answer

I had the EXACT same issue as the OP   My configuration and situation were identical   I finally narrowed it down to being an issue in WCFStorm after creating a service reference in a test project in Visual Studio and confirming that the service was working   In Storm you need to click on the  Config  settings option  NOT THE  Client Config     After clicking on that  click on the  Security  tab on the dialog that pops up  Make sure  Authentication Type  is set to  None   The default is  Windows Authentication    Presto  it works   I always test out my methods in WCFStorm as I m building them out  but have never tried using it to connect to one that has already been set up on SSL   Hope this helps someone

User · Answer

My solution  having encountered the same error message  was even simpler than the ones above  I just updated the  to basicHttpsBinding gt     lt bindings gt       lt basicHttpsBinding gt       lt binding name  quot ShipServiceSoap quot  maxBufferPoolSize  quot 512000 quot  maxReceivedMessageSize  quot 512000 quot    gt       lt  basicHttpsBinding gt       lt  bindings gt   And the same in the  section below     lt client gt       lt endpoint address  quot https   s asmx quot  binding  quot basicHttpsBinding quot  bindingConfiguration  quot ShipServiceSoap quot  contract  quot   ServiceSoap quot  name  quot ShipServiceSoap quot    gt       lt  client gt

User · Answer

Its a good to remember that config files can be split across secondary files to make config changes easier on different servers  dev demo production etc   without having to recompile code app etc  For example we use them to allow onsite engineers to make endpoint changes without actually touching the  real  files   First step is to move the bindings section out of the WPF App Config into it s own separate file   The behaviours section is set to allow both http and https  doesn t seem to have an affect on the app if both are allowed    lt serviceMetadata httpsGetEnabled  true  httpGetEnabled  true    gt    And we move the bindings section out to its own file     lt bindings configSource  Bindings config    gt     In the bindings config file we switch the security based on protocol     lt  -- None   http    -- gt     lt  -- Transport   https    -- gt     lt security mode  None   gt    Now the on site engineers only need to change the Bindings Config file and the Client Config where we store the actual URL for each endpoint   This way we can change the endpoint from http to https and back again to test the app without having to change any code   Hope this helps

User · Answer

To re-cap the question in the OP      I am connecting  to a WCF service  using WCFStorm which is able to retrieve all the meta data properly  but when I call the actual method I get       The provided URI scheme  https  is invalid  expected  http   Parameter name  via   The WCFStorm tutorials addresses this issue in Working with IIS and SSL   Their solution worked for me         To fix the error  generate a client config that matches the wcf service configuration   The easiest way to do this is with Visual Studio          Open Visual Studio and add a service reference to the service   VS will generate an app config file that matches the service   Edit the app config file so that it can be read by WCFStorm  Please see Loading Client App config files  Ensure that the endpoint  name and endpoint  contract attributes match the values in wcfstorm       Load the modified app config to WCFStorm  using the Client Config toobar button     Invoke the method   This time the method invocation will no longer fail      Item  1  last bullet in effect means to remove the namespace prefix that VS prepends to the endpoint contract attribute  by default  ServiceReference1    lt endpoint     contract  ServiceReference1 ListsService        gt    so in the app config that you load into WCFStorm you want for ListsService    lt endpoint     contract  ListsService        gt

User · Answer

Try adding message credentials on your app config like    lt bindings gt    lt basicHttpBinding gt    lt binding name  defaultBasicHttpBinding  gt      lt security mode  Transport  gt        lt transport clientCredentialType  None  proxyCredentialType  None  realm     gt        lt message clientCredentialType  Certificate  algorithmSuite  Default    gt     lt  security gt    lt  binding gt    lt  basicHttpBinding gt    lt  bindings gt

User · Answer

wsHttpBinding is a problem because silverlight doesn t support it

User · Answer

Change  from    lt security mode  None  gt    to    lt security mode  Transport  gt    in your web config file  This change will allow you to use https instead of http

User · Answer

I had same exception in a custom binding scenario  Anybody using  this approach  can check this too   I was actually adding the service reference from a local WSDL  file  It got added successfully and required custom binding was added to config file   However  the actual service was https  not http  So I  changed the  httpTransport elemet as  httpsTransport  This fixed the problem   lt system serviceModel gt   lt bindings gt      lt customBinding gt       lt binding name  MyBindingConfig  gt          lt textMessageEncoding maxReadPoolSize  64  maxWritePoolSize  16          messageVersion  Soap11  writeEncoding  utf-8  gt           lt readerQuotas maxDepth  32  maxStringContentLength  8192  maxArrayLength  16384            maxBytesPerRead  4096  maxNameTableCharCount  16384    gt         lt  textMessageEncoding gt          lt  --Manually changed httpTransport to httpsTransport-- gt         lt httpsTransport manualAddressing  false  maxBufferPoolSize  524288          maxReceivedMessageSize  65536  allowCookies  false  authenticationScheme  Anonymous          bypassProxyOnLocal  false           decompressionEnabled  true  hostNameComparisonMode  StrongWildcard          keepAliveEnabled  true  maxBufferSize  65536           proxyAuthenticationScheme  Anonymous          realm    transferMode  Buffered  unsafeConnectionNtlmAuthentication  false          useDefaultWebProxy  true    gt       lt  binding gt     lt  customBinding gt    lt  bindings gt    lt client gt     lt endpoint address  https   mainservices-certint mycompany com Services HRTest      binding  customBinding  bindingConfiguration  MyBindingConfig      contract  HRTest TestWebserviceManagerImpl  name  TestWebserviceManagerImpl    gt   lt  client gt     lt  system serviceModel gt    References   WCF with custombinding on both http and https

User · Answer

If you do this programatically and not in web config its   new WebHttpBinding WebHttpSecurityMode Transport

User · Answer

Are you running this on the Cassini  vs dev server  or on IIS with a cert installed  I have had issues in the past trying to hook up secure endpoints on the dev web server   Here is the binding configuration that has worked for me in the past  Instead of basicHttpBinding  it uses wsHttpBinding  I don t know if that is a problem for you    lt  -- Binding settings for HTTPS endpoint -- gt   lt binding name  WsSecured  gt       lt security mode  Transport  gt           lt transport clientCredentialType  None    gt           lt message clientCredentialType  None              negotiateServiceCredential  false              establishSecurityContext  false    gt       lt  security gt   lt  binding gt    and the endpoint   lt endpoint address       binding  wsHttpBinding      bindingConfiguration  WsSecured  contract  IYourContract    gt    Also  make sure you change the client configuration to enable Transport security

User · Answer

I ve added a  quot Connected Service quot  to our project by Visual Studio which generated a default method to create Client  var client   new MyWebService Client MyWebService Client EndpointConfiguration MyPort   endpointUrl    This constructor inherits ClientBase and behind the scene is creating Binding by using its own method Client GetBindingForEndpoint endpointConfiguration   public Client EndpointConfiguration endpointConfiguration  string remoteAddress                base Client GetBindingForEndpoint endpointConfiguration                     new System ServiceModel EndpointAddress remoteAddress    This method has different settings for https service and http service  When you want get data from http  you should use TransportCredentialOnly  System ServiceModel BasicHttpBinding result   new System ServiceModel BasicHttpBinding    result Security Mode   System ServiceModel BasicHttpSecurityMode TransportCredentialOnly     For https you should use Transport  result Security Mode   System ServiceModel BasicHttpSecurityMode Transport

User · Answer

I needed the following bindings to get mine to work            lt binding name  SI PurchaseRequisition ISBindingSSL  gt             lt security mode  Transport  gt               lt transport clientCredentialType  Basic  proxyCredentialType  None  realm      gt             lt  security gt           lt  binding gt

User · Answer

Adding this as an answer  just since you can t do much fancy formatting in comments  I had the same issue  except I was creating and binding my web service client entirely in code  Reason is the DLL was being uploaded into a system  which prohibited the use of config files    Here is the code as it needed to be updated to communicate over SSL      Public Function GetWebserviceClient   As WebWorker workerSoapClient     Dim binding   New BasicHttpBinding       binding Name    WebWorkerSoap      binding CloseTimeout   TimeSpan FromMinutes 1      binding OpenTimeout   TimeSpan FromMinutes 1      binding ReceiveTimeout   TimeSpan FromMinutes 10      binding SendTimeout   TimeSpan FromMinutes 1           HERE S THE IMPORTANT BIT FOR SSL     binding Security Mode   BasicHttpSecurityMode Transport      Dim endpoint   New EndpointAddress  https   myurl worker asmx        Return New WebWorker workerSoapClient binding  endpoint  End Function

User · Answer

Ran into the same issue  this is how my solution turned out at the end            lt basicHttpsBinding gt               lt binding name  VerificationServicesPasswordBinding  gt                 lt security mode  Transport  gt                 lt  security gt               lt  binding gt               lt binding name  VerificationServicesPasswordBinding1    gt           lt  basicHttpsBinding gt    I basically replaced every occurrence of Http with Https  You can try adding both of them if you prefer

User · Answer

lt  -- Binding settings for HTTPS endpoint -- gt   lt binding name  quot yourServiceName quot  gt       lt security mode  quot Transport quot  gt           lt transport clientCredentialType  quot None quot    gt           lt  -- Don t use message -- gt       lt  security gt   lt  binding gt

User · Answer

FWIW this error can happen if you are not carful when adding your service reference to the application that is calling the https service For example if you deleted your previous service reference that used to be http   example com Service svc and then recreated it so it is now https   example com service svc  If you are not careful to delete the old client and binding in the web config before recreating the service reference it will create BasicHttpBinding IService1 instead of BasicHttpBinding IService  Then when you deploy the application to the actual server it will say  https is invalid expected http  because its looking for BasicHttpBinding IService1  amp  not BasicHttpBinding IService any longer  Meanwhile you are trying all the suggestions above with no result  Just thought I would throw that out there

[c#] The provided URI scheme 'https' is invalid; expected 'http'. Parameter name: via

Examples related to c#

Examples related to wcf

Examples related to https