Databases
StackOverflow2013
Postsdbo
POWCF 4 REST service can't return a StatusDescription, only StatusCode
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POWCF 4 REST service can't return a StatusDescription, only StatusCode
    primarykey
    data
    text
    <p>I'm currently migrating my WCF RESTful service from .NET 3.5 (Starter Kit) to .NET 4. I started my project using a WCF Rest service template from Visual Studio 2010. I had to figure out how to keep my authorization scheme (formely done with RequestInterceptor) using ServiceAuthorizationManager. After some work and researching I got it done. But now I have a collateral problem. My service used to feedback my client of any processing errors using HTTP status code and a brief description. I was using WebOperationContext at many points of my service method to describe to clients what went wrong, like this:</p> <pre><code>protected void returnCode(HttpStatusCode code, string description) { WebOperationContext ctx = WebOperationContext.Current; ctx.OutgoingResponse.StatusDescription = description; ctx.OutgoingResponse.StatusCode = code; } </code></pre> <p>But in WCF 4, only StatusCode works - StatusDescription silently fails. I can't figure out why. My only guess is that WebOperationContext doesn't work in this new WCF 4 scenario, and I should be using OperationContext instead, but that also doesn't work. The following method is used in my custom class extending ServiceAuthorizationManager, informing clients a request couldn't be access because auth digest was malformed:</p> <pre><code>private void GenerateBadDigestMessage(ref OperationContext operationContext) { Message reply = Message.CreateMessage(MessageVersion.None, null, null, new DataContractJsonSerializer(typeof(object))); HttpResponseMessageProperty hrp = new HttpResponseMessageProperty(); hrp.StatusCode = HttpStatusCode.Forbidden; hrp.StatusDescription = "bad digest"; reply.Properties[HttpResponseMessageProperty.Name] = hrp; operationContext.RequestContext.Reply(reply); operationContext.RequestContext = null; } </code></pre> <p>Even by using OperationContext direclty here (insted of WebOperationContext), StatusDescription doesn't work.</p> <p>What I'm missing here? Why such a small thing can break from .NET 3.5 to 4? </p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. This table or related slice is empty.
    1. USFernando Piancastelli
    plurals
    1. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POWCF 4 REST service can't return a StatusDescription, only StatusCode
      1. USDavid Hoerster
      1. VTFavorite
    2. VO
      singulars
      1. POWCF 4 REST service can't return a StatusDescription, only StatusCode
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POWCF 4 REST service can't return a StatusDescription, only StatusCode
      1. USHemant
      1. VTFavorite
    1. COSelf-hosted or IIS? Which server version? I tested this on 4.0 with Server 2008R2 self-hosted, and it works fine (returns the Status Description as set).
      singulars
      1. POWCF 4 REST service can't return a StatusDescription, only StatusCode
      1. USnitzmahone
    2. CODid you ever find a solution? I am facing the same problem.
      singulars
      1. POWCF 4 REST service can't return a StatusDescription, only StatusCode
      1. USHemant
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload