Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>What your doing seems valid. Although I have some doubts whether I would go to those lengths.</p> <p><strong>Correction</strong></p> <p>I had said</p> <blockquote> <p>If you hadn't implemented this this additional method then the routing would have failed and would have normally returned a 404. I would be tempted to leave it with this behavior.</p> </blockquote> <p>But you are correct:</p> <p>To get it to operate as above i.e. default to a 404, you would need the following route configurations:</p> <pre><code> config.Routes.MapHttpRoute( name: "DefaultCollectionApi", routeTemplate: "api/{controller}", defaults: new { }, constraints: new { httpMethod = new HttpMethodConstraint(HttpMethod.Post) } ); config.Routes.MapHttpRoute( name: "DefaultApi", routeTemplate: "api/{controller}/{id}", defaults: new { }, constraints: new { httpMethod = new HttpMethodConstraint(HttpMethod.Get, HttpMethod.Put, HttpMethod.Delete) } ); </code></pre> <p><strong>To improve your existing approach slightly</strong></p> <p>However, if you did feel the need to start policing the combination of verbs and routes then it may be worth moving this logic into an ActionFilterAttribute. </p> <p>If you add this route at the top then it will en Assuming you use <code>"id"</code> by convention for all routes you could quickly put together a filter that looked for a value in <code>RouteValues</code> with the key of <code>id</code> and raise a 400 exception.</p> <pre><code>public class ValidVerbAndRouteAttribute : ActionFilterAttribute { public override void OnActionExecuted(HttpActionExecutedContext actionExecutedContext) { object id; if (actionExecutedContext.ActionContext.ActionArguments.TryGetValue("id", out id) &amp;&amp; actionExecutedContext.Request.Method == HttpMethod.Post) { throw new HttpResponseException(HttpStatusCode.BadRequest); } } } </code></pre>
    singulars
    1. This table or related slice is empty.
    1. POBest practice for handling an id being sent when performing a POST on an ApiController?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USMark Jones
    1. USMark Jones
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POBest practice for handling an id being sent when performing a POST on an ApiController?
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COI was having my doubts about the lengths I have went to myself - however, if I was to leave out the second Post method, I would be able to add whatever garbage I wanted to the end of the url (i.e. `POST /localhost/api/blah1234`) and it would still hit the first Post method and continue as if the extra garbage wasn't there. It does not throw a 404 as you might expect.
      singulars
      1. PO
      1. USStevie
    2. COI suppose the lack of 404 is due to my routeTemplete being `"api/{controller}/{id}"`. The API knows `{id}` is optional, so it would treat it as such and execute the first Post method in absence of the second.
      singulars
      1. PO
      1. USStevie
    3. CO@Stevie indeed. I have shown a way of altering that behavior using a route specific to collection based verbs, maybe worth trying.
      singulars
      1. PO
      1. USMark Jones
 

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