使用 WS-Addressing over https 访问 WCF 服务时面临问题

Question

I am trying to run a wcf service which i have created using ws-addressing custom binding. when i am running the application locally then getting following error. could any one point out the solution?

Error: Cannot obtain Metadata from https://localhost:8734/eTirWebocService/MessageHandlerService/mex If this is a Windows (R) Communication Foundation service to which you have access, please check that you have enabled metadata publishing at the specified address. For help enabling metadata publishing, please refer to the MSDN documentation at http://go.microsoft.com/fwlink/?LinkId=65455.WS-Metadata Exchange Error URI: https://localhost:8734/eTirWebocService/MessageHandlerService/mex Metadata contains a reference that cannot be resolved: 'https://localhost:8734/eTirWebocService/MessageHandlerService/mex'. An error occurred while making the HTTP request to https://localhost:8734/eTirWebocService/MessageHandlerService/mex. This could be due to the fact that the server certificate is not configured properly with HTTP.SYS in the HTTPS case. This could also be caused by a mismatch of the security binding between the client and the server. The underlying connection was closed: An unexpected error occurred on a send. Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host. An existing connection was forcibly closed by the remote hostHTTP GET Error URI: https://localhost:8734/eTirWebocService/MessageHandlerService/mex There was an error downloading 'https://localhost:8734/eTirWebocService/MessageHandlerService/mex'. The underlying connection was closed: An unexpected error occurred on a send. Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host. An existing connection was forcibly closed by the remote host

my app.config looks like this

enter image description here

Answer 1

Maybe you can try these steps to fix it:

1. Check the service name in the.svc file.
2. Match the name to the Service tag in the Web.config to see if it is the same.
3. Check whether the address on the Web page is different from the address on the client.

You can also check to see if the name of your CustomBinding is duplicate, and if so, set it to a different name.