Empty Response on WCF Web Service with Custom Addresses on EndPoints

[skullown]

I created a WCF web service and hosted it on IIS. The web.config looks something like this:\[code\][...]<system.serviceModel> <behaviors> <serviceBehaviors> <behavior name="[Namespace].[ServiceNameBehavior]"> <serviceMetadata httpGetEnabled="true" httpsGetEnabled="true"/> <serviceDebug includeExceptionDetailInFaults="true"/> </behavior> </serviceBehaviors> </behaviors> <services> <service name="[Namespace].[ServiceName]" behaviorConfiguration="[NameSpace].[ServiceNameBehavior]" > <endpoint address="basic" binding="basicHttpBinding" contract="[Namespace].[IService]" /> <endpoint address="secure" binding="basicHttpsBinding" contract="[Namespace].[IService]" /> </service> </services></system.serviceModel>[...]\[/code\]When I access \[code\]http://localhost/[Namespace]/[ServiceName].svc\[/code\] I get the usual web service web page indicating you have created a service, and that to test it you should call the service using svcutil.exe, etc, etc...Now.. the problem is that, as defined in the web.config, I want to use two types of connections for this web service (and actually just limit the access to those two, so disabling the default \[code\].svc\[/code\] call) but when I go to \[code\]http://localhost/[Namespace]/[ServiceName].svc/basic\[/code\] or \[code\]https://localhost/[Namespace]/[ServiceName].svc/secure\[/code\] I get a blank page nor can I access the services from a local-hosted PHP page.Is it normal that these bindings behave like this? If not, How can I fix it?