Last post Jul 01, 2015 01:25 AM by Tracy Dj
Jun 29, 2015 01:54 PM|lhowe|LINK
I've been searching for this error, and found plenty on it, but nothing seems to be clearing the error up for me. I' trying to POST to a WebHttpBinding service running under SSL on IIS6. However, no matter what I try, I keep getting "Could not find a base
address that matches scheme https for the endpoint with binding WebHttpBinding. Registered base address schemes are ". My baseAddressPrefixFilters is viable as SSL. I know this because I created a test classic ASP page and called it successfully via web
browser using HTTPS. When I try not using HTTPS, and just use HTTP, I get the standard error message indicating it must be accessed over HTTPS. Therefore, I know that I have the IIS side of it set up right. It's also not my first time setting up SSL on
a web server, so I know what I'm doing on that end. I just apparently don't know what I'm doing on the WCF configuration side. By the way, this web service works on my test server WITHOUT using SSL. I've made the changes that I'm seeing in the various posts
online to make it work via HTTPS, but nothing seems to help. This is also using the 3.5 framework.
Here is my web.config system.serviceModel section (my website prefix domain has been modified here for security)
<service name="WcfService1.Service1" behaviorConfiguration="WcfService1.Service1Behavior">
<!-- Service Endpoints -->
<binding name="webBinding" transferMode="Streamed" maxBufferSize="10485760" maxReceivedMessageSize="10485760" >
<security mode="Transport" />
<serviceMetadata httpGetEnabled="false" httpsGetEnabled="false" />
Hopefully, someone will see what I'm doing wrong here.
Jun 29, 2015 03:58 PM|lhowe|LINK
Well, I just found the solution. According to this information (http://stackoverflow.com/questions/2200105/wcf-service-could-not-be-activated), IIS doesn't need
the baseAddressPrefixFilters as the site configuration takes care of it. Didn't make much sense to me, but I removed the base address config, and all of a sudden it worked. Not sure why it's ever needed then, but at least it seems to have resolved my problem.
Jun 30, 2015 05:38 AM|Tracy Dj|LINK
According this case , in my opinion is that you will need to create service with two endpoints. One endpoint will use
HTTP (binding without transport security) and second endpoint will use HTTPS (binding with transport security).
You will also have to configure your IIS to support both HTTP and HTTPS (assign certificate).
For more information, please try to refer to following articals:
#config for both http and https:
Note:If you want to use baseAddressPrefixFilters in web.config, you must setup IIS too.
I hope that will be helpful to you.
Jun 30, 2015 08:08 AM|lhowe|LINK
Hi Tracy Dj,
Thanks for responding, however, as I said in my follow-up post, it appears that I have resolved my issue simply by removing the baseAddressPrefixFilter tag. Everything seems to be working now without it. Actually, I'm not sure why you would suggest configuring
both http and https. I don't need, nor want, http with this particular service. I only want it accessible via SSL, and it was only used without SSL on the test server as we were developing the web service. My only confusion is when do you need the baseAddressPrefixFilter,
if IIS takes care of it itself?
Jul 01, 2015 01:25 AM|Tracy Dj|LINK
Sorry，I didn't see you solved the problem. So,maybe the solution I provided is not what you need.
If you need, may be you can refer to this artical:
Apologize again for confusion to you.