Attribute routing recognize optional query string parameters

Question

I have a API action:

 [HttpGet, Route("{id}/overview/")]
 public async Task<HttpResponseMessage> Overview(string id, DateTime from, DateTime? to)
{
...
}

As you noticed, to is optional parameters, but when I make request:

'/api/cream/3d7dd454c00b/overview?from=2016-09-04T18:00:00.000Z

I got 404 error. If I delete to from parameters: public async Task<HttpResponseMessage> Overview(string id, DateTime from)

then all works fine. How to force it work with to parameters?

In your example to is not optional. You will need to change it to an optional argument. ie Overview(string id, DateTime from, DateTime? to = null). That is all. — Nkosi
– Nkosi, Commented Sep 19, 2016 at 8:51

jimpaine · Accepted Answer · 2016-09-19 08:51:14Z

8

Use the FromUri attribute and make to optional



    [HttpGet, Route("{id}/overview/")]
     public async Task Overview(string id, [FromUri]DateTime from, [FromUri]DateTime? to = null)
    {
    ...
    }

To expand on this the id parameter is picked up because you have specified it in your route, the framework has seen a matching route and tried to call the method which matches, even though the route is missing the remaining parameters it has tried to pull them from the query string.

You then get your 404 as no method matched your call, this was due to the to DateTime being nullable but not optional.

Hope this helps

edited Sep 19, 2016 at 8:51

answered Sep 19, 2016 at 8:38

jimpaine

8876 silver badges11 bronze badges

Sign up to request clarification or add additional context in comments.

1 Comment

user348173 Over a year ago

Yes, to = null fixed the issue, thanks for the answer.

Collectives™ on Stack Overflow

Attribute routing recognize optional query string parameters

1 Answer 1

1 Comment

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

1 Comment

Your Answer

Sign up or log in

Post as a guest

Related