I have a simple WCF service hosting on a server on IIS6 on the network.
When I use the following binding on a server in my network I got 404, if only the client is not credential type, then it works, it works on my machine, because Windows authentication fails on the server, 404 actually means that it can not even see the endpoint, if it determines how to proxy the problem.
& lt; BasicHttpBinding & gt; & Lt; Compulsory name = "HTTP windows attestation" MaxReserveWiseSism = "1048576" Bypass Proxy ONOLOKAL = "TRUE" USEUDEWebProxy = "Fictitious" & gt; & Lt; Safety Mode = "Transport Credential Only" & gt; & Lt; Transport Customer Credential Type = "Windows" Proxy Credential Type = "None" /> & Lt; / Safety & gt; & Lt; / Binding & gt; & Lt; / BasicHttpBinding & gt;
thanks
This is probably related to security because it Works when you change client credentials type.
You get 404, to improve security, the system is saying "yes, there is a file with that name, but you do not have permission to view it."
It seems that the user who makes the WCF call does not have access to the SVC file, but the user running the asp.net process uses the user who is running the asp.net process, that is used for random clients.
Belongs to the default setting above.
Comments
Post a Comment