Handling case sensitive URLs in Proxy using DevOps

We have an implementation use case where we would like to handle all consumer requests irrespective of the case (Upper, Lower, combination) to be directed to corresponding proxies.

The idea is to have this handled through a DevOps pipeline which converts Swagger Specs to Edge proxies, without having to manually add the "CaseInsensitive" condition in each of the proxy methods.

So we have taken an approach to have a Master proxy (as described in another community post), to convert the incoming request URL to lower case, so the relevant proxy can be invoked.

What we would like to confirm is the naming conventions used to create this master proxy.

We are trying different approaches like "/api", "/1", "/v1" for master proxy path, and would like to know how other customers handle this use case.

Each of those approaches have pros & cons, like

  1. Creating multiple master proxies to handle upper & lower case for "/api", "v1".
  2. Do we have implementations using "/1" for master proxies?
  3. how do we handle versioning in url? (maybe have /api/v1/proxy)

It would help if we can have real implementation examples on how this was achieved.

PS. Completely fine to know if there is an altogether different approach to handle case sensitive URLs other than having a master proxy.

Thanks,

Shshank

1 0 210
0 REPLIES 0