By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
424,984 Members | 1,016 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 424,984 IT Pros & Developers. It's quick & easy.

WCF - ASP.NET Development Server issue when HTTPS endpoint exists

P: n/a
I have a WCF Web Service that I develop using the ASP.NET Development
Server in Visual Studio. In release, the web service will support both
HTTP and HTTPS. Initially I had only HTTP configured in my web.config
file, but have now added the HTTPS endpoints and bindings. When I do
this, I now get an error when trying to connect to the development
server from my client using HTTP. On the client side, I get the
error..

System.ServiceModel.CommunicationException: The server did not provide
a meaningful reply; this might be caused by a contract mismatch, a
premature session shutdown or an internal server error.

The client works fine when web service runs under IIS with the
following web.config. Here are the bindings and endpoints that I have
in the web.config...

<bindings>
<basicHttpBinding>

<!-- HTTP binding -->
<binding name="basicHttp" >
</binding>

<!-- HTTPS binding -->
<binding name="basicHttps" >
<security mode="Transport">
<transport clientCredentialType="Windows" />
</security>
</binding>

</basicHttpBinding>
</bindings>

<services>
<service name="myServer">

<!-- HTTP endpoint -->
<endpoint binding="basicHttpBinding"
bindingConfiguration="basicHttp"
name="httpAspNet" contract="WebService.IWebApp" />

<!-- HTTPS endpoint -->
<endpoint
binding="basicHttpBinding" bindingConfiguration="basicHttps"
name="httpsAspNet" contract="WebService.IWebApp />

</service>
</services>

If I comment out the HTTPS endpoint, then all works ok in the client
with developement web server. Currently, I have to checkout the
web.config file from verison control during development, comment out
the endpoint. Then, make sure that I do not check it in :), or I will
break the release build.

I do not require a HTTPS connection for my client during development,
so have been using HTTP, but just the presence of the HTTPS endpoint
even if not accessed is causing the error.

Anybody else have this issue and suggest a solution?

Thanks,
Ron

Jun 7 '07 #1
Share this question for a faster answer!
Share on Google+

This discussion thread is closed

Replies have been disabled for this discussion.