Going from dev to live, where the dev system referenced dev version of web services, but the live system has to reference live versions which are HTTPS i recieved this error;
The provided URI scheme ‘http’ is invalid; expected ‘https
This is resolved simply by updating the web.config file and setting the security tag’s mode attribute from None to Transport;
<bindings> <wsHttpBinding> <binding name="WSHttpBinding_IWSHttpService" closeTimeout="00:01:00" openTimeout="00:01:00" receiveTimeout="00:10:00" sendTimeout="00:01:00" bypassProxyOnLocal="false" transactionFlow="false" hostNameComparisonMode="StrongWildcard" maxBufferPoolSize="524288" maxReceivedMessageSize="65536" messageEncoding="Text" textEncoding="utf-8" useDefaultWebProxy="true" allowCookies="false"> <readerQuotas maxDepth="32" maxStringContentLength="8192" maxArrayLength="16384" maxBytesPerRead="4096" maxNameTableCharCount="16384" /> <reliableSession ordered="true" inactivityTimeout="00:10:00" enabled="false" /> <security mode="Transport"> <transport clientCredentialType="None" proxyCredentialType="None" realm="" /> <message clientCredentialType="None" negotiateServiceCredential="true" algorithmSuite="Default" establishSecurityContext="true" /> </security> </binding> </wsHttpBinding> </bindings>
The provided URI scheme ‘http’ is invalid; expected ‘https.
Related posts:
#1 by KevinSchubert on July 23, 2009 - 23:17
Sometimes it’s really that simple, isn’t it? I feel a little stupid for not thinking of this myself/earlier, though.
#2 by shawson on July 24, 2009 - 16:24
haha don’t feel bad- i spent an hour or so on this!
#3 by Naziya Khan on September 4, 2009 - 01:07
I am getting the same error.
But my security mode is already set to TransportWithMessageCredentials
Service is running on https and the client’s app.config has https too
Whats wrong….. grrrrrr
#4 by shawson on September 8, 2009 - 14:12
hmm- are you sure it’s set correctly- i set the security tag’s mode property simply to “Transport”?
#5 by essay writers on October 9, 2009 - 15:31
Still the same problem
#6 by Michael on January 18, 2010 - 23:00
It really was that simple! After a few hours…Thanks
#7 by DotNetCoder on January 14, 2011 - 21:47
Change the security mode=”Transport” to security mode=”None”
or change the endpoint to https