basichttpbinding

WCF - Streaming file upload over http

僤鯓⒐⒋嵵緔 提交于 2019-12-06 12:13:04
问题 I am trying to build a WCF service that will allow my WPF desktop clients to upload files to a server. I adapted a code sample from The Code Project (WCF Streaming: Upload/Download Files Over HTTP) and I've looked at several SO posts as well, but can't seem to get this working. When I execute the code, it fails with a null reference exception at the point that the server tries to read the stream that has been passed through the interface. At this point, I am rather lost and don't know how to

Cannot process the message because the content type 'application/soap+msbin1' was not the expected type 'text/xml

自作多情 提交于 2019-12-06 10:43:01
问题 I have a Silverlight application that calls a WCF successfully in my development environment (Win 7). When i inspect the content type returned in Fiddler, it is showing as below. HTTP/1.1 200 OK Cache-Control: private Content-Length: 18849 Content-Type: text/xml; charset=utf-8 Server: Microsoft-IIS/7.5 X-AspNet-Version: 4.0.30319 X-Powered-By: ASP.NET Date: Mon, 01 Sep 2014 14:59:01 GMT However, as soon as i deploy the application in my QA server (IIS 6.0) the call to the WCF service fails

WCF NetTCPBinding vs HttpBinding difference in data sent on wire

冷暖自知 提交于 2019-12-06 03:37:37
问题 Say I have a service exposing two end points, 1st is a NetTCPBinding the second is any flavour of HttpBinding. They both implement exactly the same service contract. What is the difference in what is sent on the wire? Using netTcp is my message still serialised to XML ? Or some binary representation of my objects? In terms of what receives the messages what is the difference? Will the http endpoint only understand http commands (get/post etc) where as the nettcp end point understands

calling wcf webservice using basichttpbinding without REST or JSON

扶醉桌前 提交于 2019-12-06 02:25:32
I have a wcf webservice that is exposed through wsHTTPBinding and basicHTTPBinding. The latter specifies it's endpoint address as being "/basic" as in the following: <endpoint address="/basic" binding="basicHttpBinding" bindingConfiguration="theAwesomeBasicHttpServerBinding" contract="LOServices.Proxy.ServiceContracts.ILOService"> <identity> <servicePrincipalName value="HTTP/MY_MACHINE_NAME" /> </identity> </endpoint> the binding is defined as follows: <basicHttpBinding> <binding name="theAwesomeBasicHttpServerBinding" maxReceivedMessageSize="5000000"> <security mode="TransportCredentialOnly">

WCF client configuration for 3rd party SOAP 1.1 service with plain text username credentials over SSL

守給你的承諾、 提交于 2019-12-05 18:02:23
I am trying to connect to a third party SOAP 1.1 service that requires SSL security and username/password credentials. An example of what is expected is: <soapenv:Header> <wsse:Security> <wsse:UsernameToken> <wsse:Username>username</wsse:Username> <wsse:Password>password</wsse:Password> </wsse:UsernameToken> </wsse:Security> </soapenv:Header> My client configuration is as follows: <system.serviceModel> <bindings> <basicHttpBinding> <binding name="thirdpartyservicebindingconfig"> <security mode="TransportWithMessageCredential"> <message clientCredentialType="UserName" algorithmSuite="Default" /

Wcf Basic authentication

蓝咒 提交于 2019-12-05 09:54:10
问题 Having some trouble using basic authentication with a simple test Wcf service. I am getting an exception: The requested service, 'http://qld-tgower/test/Service.svc' could not be activated. See the > server's diagnostic trace logs for more information. And in the trace log it shows: The authentication schemes configured on the host ('Basic') do not allow those configured on the binding 'BasicHttpBinding' ('Anonymous'). Please ensure that the SecurityMode is set to Transport or

Cannot process the message because the content type 'application/soap+msbin1' was not the expected type 'text/xml

白昼怎懂夜的黑 提交于 2019-12-04 17:02:29
I have a Silverlight application that calls a WCF successfully in my development environment (Win 7). When i inspect the content type returned in Fiddler, it is showing as below. HTTP/1.1 200 OK Cache-Control: private Content-Length: 18849 Content-Type: text/xml; charset=utf-8 Server: Microsoft-IIS/7.5 X-AspNet-Version: 4.0.30319 X-Powered-By: ASP.NET Date: Mon, 01 Sep 2014 14:59:01 GMT However, as soon as i deploy the application in my QA server (IIS 6.0) the call to the WCF service fails with below error (again according from Fiddler) HTTP/1.1 415 Cannot process the message because the

BasicHttpBinding with TransportWithMessageCredential and clientCredentialType=“Windows”

我是研究僧i 提交于 2019-12-04 15:31:20
I am using this binding configuration on client and server: <basicHttpBinding> <binding name="BasicHttpBinding_IService1"> <security mode="TransportWithMessageCredential"> <transport clientCredentialType="Windows" /> </security> </binding> </basicHttpBinding> The client credentials seem to not be passed automagically (or are they?) this way like i assumed, so i need to know how to set them by myself. Will this even work? Anand You have to enable Windows Authentication on IIS . Look at the below link for how to do it. Also, I checked the MSDN web site, the key difference between your config and

Wcf Basic authentication

六眼飞鱼酱① 提交于 2019-12-04 00:06:26
Having some trouble using basic authentication with a simple test Wcf service. I am getting an exception: The requested service, 'http://qld-tgower/test/Service.svc' could not be activated. See the > server's diagnostic trace logs for more information. And in the trace log it shows: The authentication schemes configured on the host ('Basic') do not allow those configured on the binding 'BasicHttpBinding' ('Anonymous'). Please ensure that the SecurityMode is set to Transport or TransportCredentialOnly. Additionally, this may be resolved by changing the authentication schemes for this

Does a WCF service with basicHttpBinding create a new connection for each request?

半城伤御伤魂 提交于 2019-12-03 13:49:16
问题 I have a Silverlight client calling a WCF Service on an IIS web server. It uses the default basicHttpBinding setting for the calls. My client code has the usual Visual Studio generated proxy that is generated when using the 'Update Service Reference' menu option. Does every call to the service using that proxy use the same connection? Or does it create a connection each time a call is made and then close it down once the reply is received? As the client is actually making a SOAP call over