Home/ Questions/Q 7655061
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-31T12:24:58+00:00

I’m really confused by this… still. I asked a similar question to this a

  • 0

I’m really confused by this… still.

I asked a similar question to this a while before, but i’ll ask it even simpler now.

I see this in a lot of samples and tutorials. How could you put [Bind(Exclude=”ID”)] on an entire Model, and expect to do Edits on the model? If you get pack all the properties of a model on a POST but not the ID, then how do you know which ID to edit?

Even if i’m using ViewModels… i’m probably creating them without IDs. So in that case… also… how do I know which ID was updated on an Edit?

Yes, i understand that there is a “security” element to this. People can hijack the ID… so we need to keep people from updating the value during a POST. But… what is the correct way to handle edits then? What’s common practice?

I feel like i’m missing something VERY trivial.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    In MVC requests are processed by the model binder when the client makes a request. If you include models on your controllers then, as far as I’m aware, you actually have to specify the model you wish to bind to by prefixing your arguments with the model name (unless you only have one argument which is the model)

    SomeModel_ID

    Now, in some cases you might want to exclude certain properties from being bound to because they pose a security risk, which you seem to be happy with as a concept. We will exclude ID on the model, preventing any client request from posting this value in plain text.

    Now why might we exclude an entire model? Well not all controller arguments are pre-processed by a model binder. RedirectToAction for example does not pass through the model binder, so it is conceivable in this instance for you to create a new model in a POST controller action, and redirect to a GET controller action, passing along a sanitised model. That model cannot be populated by the client, but we are free to populate it ourselves on the server side.

    The only time I bind to a model is when I have a view model and an associated editor for that model. This makes it really easy to inject a common editor into a page and to encapsulate those properties. If you have to exclude certain properties from being bound to I would argue that you are doing it wrong.

    Update

    Following your comments I think I can see why you might be confused. The model bind excluder prevents the client from ever setting a model property. If you need this property to do your updating then you simply can’t exclude it. What this does mean then is that the user could potentially post back any ID. In this case you should check that the user has permission to be modifying any objects or database records associated with this ID before serving the requested update. Validating the arguments is a manual process. You can use data annotations for validating inputs, but this isn’t likely to help very much with access permissions. It’s something you should be checking for manually at some stage.

    • 0