CODEWITHSUNDEEP
c#urlasp.net-web-apiasp.net-web-api-routingrouteattribute
abatishchev
abatishchev

Reputation: 100358

How to support both 'regular' and 'readable' urls in Web API attribute rouring?

I have ASP.NET Web API 2.1 project with attribute routing enabled, and a controller action decorated as following:

[Route("api/product/barcode/{barcodeType}/{barcode}")]
public async Task<IHttpActionResult> GetProduct([FromUri] BarcodeSearchCriteria searchCriteria)

where BarcodeSearchCriteria is a complex type:

public class BarcodeSearchCriteria
{
    public string Barcode { get; set; }

    public string BarcodeType { get; set; }
}

It works well for a 'regular' url like this:

/api/product/barcode/EAN/0747599330971

but how in the same time support an url like this:

/api/product/barcode/?barcodeType=EAN&barcode=0747599330971

I used to use it in my *.webtest before switched to 'readable` mode.

Upvotes: 0

Views: 81

Answers (2)

Kiran
Kiran

Reputation: 57999

you could have 2 routes in this case:

[Route("api/product/barcode")] //expects values from query string
[Route("api/product/barcode/{barcodeType}/{barcode}")] //expects value from route
public async Task<IHttpActionResult> GetProduct([FromUri] BarcodeSearchCriteria searchCriteria)

Upvotes: 1

ssilas777
ssilas777

Reputation: 9764

It looks like there is no route defined for the regular Url with query string parameters.

Try making the route parameters optional like this.

[Route("api/product/barcode/{barcodeType=""}/{barcode=""}")]
public async Task<IHttpActionResult> GetProduct([FromUri] BarcodeSearchCriteria searchCriteria)

So it should also match the route template api/product/barcode route.

Haven't tested, though hope you got my point.

Upvotes: 0

Related Questions