title: API controller route attribute issue
body: <p>I have an issue with an api controller attribute routing. The API receives a get request containing a scanned barcode to the route: <code>&quot;api/[controller]/{userId}/{barcodeId}&quot;</code>. Where the barcode is like: 0015A765248.</p>
  <p>But we now have some new barcodes coming in this format: BBRT058/639.</p>
  <p>I've found out through debugging that the extra <code>/</code> in the new barcode is causing the issue as the API controller is now not being accessed.</p>
  <p>As I think it is trying to reach controller:  <code>&quot;api/[controller]/{userId}/{barcodeId}/{barcodeID}&quot;</code></p>
  <p>Which doesn't exist. Is it possible to modify the API controller route attribute to accept the barcodeId containing the additional <code>/</code>?</p>
  <p>Actually modifying the new barcode style in any way code wise is not an option I am told.</p>
  <p>I have considered creating a new controller to accept the new barcode: <code>&quot;api/[controller]/{userId}/{barcodeIdpart1}/{barcodeIDpart2}&quot;</code> for example.
  But i'm not sure if creating a new controller that is a duplicate of the current one, with the only difference being the routing is a good idea. Also both barcode formats are likely still going to be used in the future.</p>