all groups > dotnet web services > january 2008 >
You're in the

dotnet web services

group:

WCF basicHttpBinding


WCF basicHttpBinding Philip
1/23/2008 7:21:55 PM
dotnet web services:
I have created a WCF Service with a basicHttpBinding. It is not easy for me
to deploy a server certificate, so this is the reason I am using a
basicHttpBinding..... with a simple username/password authentication, using
the asp.net membership subsystem.

I am hosting my WCF Service under IIS 6.0. I have three Http host bindings,
and a single Https host bindings. After much searching on the Internet I
concluded that I needed to write a Custom Host Factory, which is referenced
from the WCF ".svc" file. The Custom Host Factory selects one of the Http
host bindings and the single Https host binding and returns these two host
bindings in the Custom Host Factory module.

I was quite surprised that with its quite robust WCF architecture that I
needed to write a Custom Host Factory for such a common network configuration.

Am I way off base here ?.... are there any new WCF developments which make
the Custom Host Factory no longer necessary ?

--
RE: WCF basicHttpBinding Philip
1/28/2008 6:12:23 PM
I can create a WCF proxy fine....in the manner you described....this is not
the issue... however I need the the Custom Host Factory when executing the
actual WCF service. Normally....it would work under IIS 6.0 without the need
for a Custom Host Factory...however if there are multiple IP Addresses and/or
Domain Names mapped to the web site then the Custom Host Factory is necessary.

I am only submitting this question because after searching the Internet
....several postings confirmed what I needed to do with the Custom Host
Factory.... however I would like confirmation from the MSFT Managed
Newsgroups.

--
Philip


[quoted text, click to view]
RE: WCF basicHttpBinding Prashant Brall
1/29/2008 1:42:33 AM

[quoted text, click to view]

Hi Philip,
I don't think so you need custom host factory. IIS 6.0 can easily host these webservices with and with out https.May be it is in your IIS configuration you have forced it to use https.

Otherwise from a browser you should be able to do something like this http://server/myservices/myservice.svc and https://server/myservices/myservice.svc and you should see the metadata page. If you get an error make sure you have mex binding ( metadata exchange) enabled and then you should be able to generate proxy from svcutil.exe utility.

I have deployed numerous WCF web services with https and http support at the same time and was able to generate proxy classes with out writing any hosting or host factory.

Can you describe in more details what are steps you are taking to deploy the web services.

Kind regards

Prashant Brall
PrashantBrall@hotmail.com

BizTalk Utilities - Frustration free BizTalk Adapters
AddThis Social Bookmark Button