In the service config file, the "name" attribute is missing from the element behaviors.
In the service config file, the "name" attribute is missing from the element and there should be a reference to this name in the service element.
Would you believe me if I told you that when I add a name to my behavior, the WCFTestClient gives me the error: "Error: Cannot obtain Metadata. Metadata contains a reference that cannot be resolved. Content Type application/soap+xml; charset=utf-8 was not supported by service.
The client and service bindings may be mismatched. The remote server returned an error: (415) Unsupported Media Type. HTTP GET.
The HTML document does not contain Web service discovery information. " This is why I didn't include a name for my behavior. – DaleyKD May 26 '10 at 15:11 I'm still not sure what the true solution was to this issue, but I was able to get my ORIGINAL problem resolved, making this issue moot.
FWIW, it seems as though I was able to get rid of the above error by making SURE my service used behaviorConfiguration. Thanks! – DaleyKD May 26 '10 at 19:53.
If the latter, the only thing I would recommend is to set the size of maxReceivedMessageSize to a value that is as large as the largest value you expect the service to need, so you limit your exposure to DDOS attacks.
I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.