Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • Home
  • SEARCH
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 6004379
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 23, 20262026-05-23T01:15:19+00:00 2026-05-23T01:15:19+00:00

I have a WCF Web Api Restful webservice. I want every single service call

  • 0

I have a WCF Web Api Restful webservice.

I want every single service call to take an optional parameters: suppress_status_codes. Is there a way to do this wihtout adding the parameter and handling to every end point like:

[WebGet(UriTemplate = "{somearg1}/{somearg2}/?supress={suppressStatusCodes}")
public HttpResponseMessage<string> SomeEndPoint(string somearg1, long somearg2, bool suppressStatusCodes)
{    
     // handle suppress status codes
     // do rest of call

The purpose of suppress_status_code is for Flash integration. If a webservice returns anything other than a 200 flash has an impossible timie processing the message body so I need to be able to return a “200” with an error and error status code in the HttpResponseMessage if supress_status_codes is true.

Twitter’s api has an identical optional parameter for this reason.

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-05-23T01:15:19+00:00Added an answer on May 23, 2026 at 1:15 am

    Creating a HttpOperationHandler would allow you to process the optional query parameter in a single place. However, if your Operation needs to know whether or not the SuppressStatusCodes has been set, then the easiest way to access it is via a parameter on the operation signature.

    Depending on what you need to do, it may be possible to do all of the processing in your custom HttpOperationHandler. Can you describe the impact of SuppressStatusCodes on response?


    Update:
    This could actually be done at a higher layer using a HttpMessageHandler. You could check the url for the query param and change the status code directly. Here is a completely untested example of how it could be done:

        public class StatusKillerMessageHandler : DelegatingChannel {
        public StatusKillerMessageHandler(HttpMessageChannel innerChannel)
            : base(innerChannel) {
        }
    
        protected override Task<HttpResponseMessage> SendAsync(HttpRequestMessage request, CancellationToken cancellationToken) {
    
            bool suppressStatusCode = (request.RequestUri.AbsoluteUri.ToLower().Contains("suppress=true"));
    
            return base.SendAsync(request, cancellationToken).ContinueWith<HttpResponseMessage>(task => {
    
                       var response = task.Result;
                       if (suppressStatusCode) {
                            response.StatusCode = HttpStatusCode.OK;
                       }
                       return response;
                    });
        }
    }
    
    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

I have a WCF web service, and I want to use Basic authentication. I
I have build an APi which is a WCF Service. In the web.config for
I have a WCF Web Service which is referenced from a class library. After
I have a wcf web service and I need to provide the client with
I have a WCF web-service and a Silverlight app displaying data from that service.
So I came across an interesting problem today. We have a WCF web service
I have a simple WCF Web service. It's hosted on IIS under the default
I have a silverlight 2 beta 2 application that accesses a WCF web service.
I have a website that talks to a remote WCF web service. Both use
I have a Linux/c client app that connects to a WCF web service over

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.