Databases
StackOverflow2013
Postsdbo
POIs it possible to change ASP.NET MVC 3 route constraints such that they return 400 Bad Request with JSON bodies?
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POIs it possible to change ASP.NET MVC 3 route constraints such that they return 400 Bad Request with JSON bodies?
    primarykey
    data
    text
    <p>I am developing some REST resources using the ASP.NET MVC 3 platform. So far, its been great, I love the flexibility of MVC 3, and it is a breeze to build REST services with it. One area where I have been having a difficult time are the route constraints in Global.asax. For one, they never seem to work properly (including one ALWAYS returns 404, even if the input most definitely meets the requirements of the constraint...but thats another question). </p> <p>Second, and more importantly, the result returned when a constraint fails is always an HTML page. Assuming the constraints work, having the result be HTML really throws a wrench in the mix when all of the consumers of these REST services will be accepting data types, such as application/json, text/xml, possibly bson, etc. I really need to be able to address errors in our clients directly, rather than simply blowing up and logging the html for sideband resolution. </p> <p>Is it possible to change what gets returned in response to a route constraint? Is it possible to make whats returned dynamic, such that if the client issuing the request only accepts application/bson, we can generate an acceptable response, rather than simply generating a canned response of a single mime type?</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. This table or related slice is empty.
    1. USjrista
    plurals
    1. This table or related slice is empty.
    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
    1. VO
      singulars
      1. POIs it possible to change ASP.NET MVC 3 route constraints such that they return 400 Bad Request with JSON bodies?
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POIs it possible to change ASP.NET MVC 3 route constraints such that they return 400 Bad Request with JSON bodies?
      1. USBrian Rogers
      1. VTFavorite
    3. VO
      singulars
      1. POIs it possible to change ASP.NET MVC 3 route constraints such that they return 400 Bad Request with JSON bodies?
      1. USjrista
      1. VTBountyStart
    1. COCan you explain why you couldn't use a catch-all route that maps to a controller under your control? For example, my blog engine (FunnelWeb) uses this to show a Search page instead of a 404. see http://wallaceturner.com/blah/blah2 this could trivially be changed to return a JSON string.
      singulars
      1. POIs it possible to change ASP.NET MVC 3 route constraints such that they return 400 Bad Request with JSON bodies?
      1. USwal
    2. COHadn't considered of the catch-all route. I'll have to check it out...however I'm curious if I would have error information from previous routes? If a route fails due to THAT ROUTES constraints, I want to send back a message that indicates the problem, so the client will know what went wrong. The catch-all route may be a partial solution, but if I can't access any information that explains why routing failed, it would remain just a partial fix.
      singulars
      1. POIs it possible to change ASP.NET MVC 3 route constraints such that they return 400 Bad Request with JSON bodies?
      1. USjrista
    3. CO`but if I can't access any information that explains why routing failed` Can't your unit tests cover this? routeDebugger etc? its impossible to determine what route you think your clients(not under your control) were trying to go down. Actually, I kind of see a situation you might want to handle - to see if we're on the same page could you give an example where the catch-all wouldn't work? it sounds like you might need to have catch-all's for each of your routes/controller pairs...
      singulars
      1. POIs it possible to change ASP.NET MVC 3 route constraints such that they return 400 Bad Request with JSON bodies?
      1. USwal
 

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