ASP.NET Web API

Feedback on ASP.NET Web API

You've used all your votes and won't be able to post a new idea, but you can still search and comment on existing ideas.

There are two ways to get more votes:

  • When an admin closes an idea you've voted on, you'll get your votes back from that idea.
  • You can remove your votes from an open idea you support.
  • To see ideas you have already voted on, select the "My feedback" filter and select "My open ideas".
(thinking…)

Enter your idea and we'll search to see if someone has already suggested it.

If a similar idea already exists, you can vote and comment on it.

If it doesn't exist, you can post your idea so others can vote on it.

Enter your idea and we'll search to see if someone has already suggested it.

  • Hot ideas
  • Top ideas
  • New ideas
  1. Use Reflection to Auto Populate the Allow Header

    Based on the current Route being executed, it should be possible to detect HTTP methods the same route supports and therefore populate the Allow header in the response. e.g. whilst performing a GET on /api/values it should be possible to detect that the route supports both GET and POST (in fact the code I presume already has this list so that it knows which Action to call). The Allow header could then be populated with GET, POST.

    The icing on the cake would be that the Authorize attribute is still checked so if the caller does not have permission to…

    9 votes
    Vote
    Sign in
    Check!
    (thinking…)
    Reset
    or sign in with
    • facebook
    • google
      Password icon
      I agree to the terms of service
      Signed in as (Sign out)
      You have left! (?) (thinking…)
      under review  ·  3 comments  ·  Flag idea as inappropriate…  ·  Admin →
    • Mono-For-Android-compatible version of Web Api client

      The current Web Api Client is not compatible with Mono For Android, and trying to use HttpWebRequest and OData from Android mobile app. is a pain. Not sure about the amount of effort involved, but the author of Json.Net recently provided an mfa-compatible version, packaged as a Portable Class Library.

      7 votes
      Vote
      Sign in
      Check!
      (thinking…)
      Reset
      or sign in with
      • facebook
      • google
        Password icon
        I agree to the terms of service
        Signed in as (Sign out)
        You have left! (?) (thinking…)
        under review  ·  1 comment  ·  Flag idea as inappropriate…  ·  Admin →
      • Authorization on $expand functionality

        Currently, there is no way to influence in what way $expand binds additional models. I would very much like to have some control over what models are binded, in order to apply authorization on these binded models.

        Half a year ago I already created a StackOverflow thread (http://stackoverflow.com/questions/18254600/modify-binding-of-expand-function-when-unauthorized) with the exact same problem. Since I think that there is not enough attention paid to this problem, I've created this UserVoice thread.

        5 votes
        Vote
        Sign in
        Check!
        (thinking…)
        Reset
        or sign in with
        • facebook
        • google
          Password icon
          I agree to the terms of service
          Signed in as (Sign out)
          You have left! (?) (thinking…)
          0 comments  ·  ASP.NET Web API  ·  Flag idea as inappropriate…  ·  Admin →
        • Ability to change the filter on the Server

          In WebAPI we are Mostly returning a VM, which kind of flattens hierarchy.
          CountryTable with CountryID,
          StateTable with StateID
          CityTable with CityID

          Now Address Table has those fields as Foreign Keys(CountryID,StateID,CityID)

          If i want to provide Filtering/Paging/Sorting on Address Type for Country,State,City there is no way to do that. Say i want to filer Address by Specific Country/State etc.

          Would be Nice that we get intercept, but at the same time be able to modify Columns Names in the filter so that proper filtering is applied.

          3 votes
          Vote
          Sign in
          Check!
          (thinking…)
          Reset
          or sign in with
          • facebook
          • google
            Password icon
            I agree to the terms of service
            Signed in as (Sign out)
            You have left! (?) (thinking…)
            0 comments  ·  ASP.NET Web API  ·  Flag idea as inappropriate…  ·  Admin →
          • Error in WebApi 2 Attribute Routing documentation

            This page refers to a property of an attribute routing being called RouteName when it is just called Name.

            [Route("api/books/{id}", RouteName="GetBookById")]

            should be

            [Route("api/books/{id}", Name="GetBookById")]

            http://www.asp.net/web-api/overview/web-api-routing-and-actions/attribute-routing-in-web-api-2#route-names

            2 votes
            Vote
            Sign in
            Check!
            (thinking…)
            Reset
            or sign in with
            • facebook
            • google
              Password icon
              I agree to the terms of service
              Signed in as (Sign out)
              You have left! (?) (thinking…)
              0 comments  ·  Flag idea as inappropriate…  ·  Admin →
            ← Previous 1 2 Next →
            • Don't see your idea?

            ASP.NET Web API

            Feedback and Knowledge Base