How can we improve Azure API Management?

apim should allow more than 260 characters for URL path segments

API definitions which have an ID as one path segment can have path segments which are larger than 260 characters (which is a windows limitation). Unfortunately this limitation is also part of the apim service and can be inceased by the product team on request. Why not setting it to a larger value as default or let me set an option like (windows compatible path length) when creating the instance?

This problem is very critical if you face it because the apim service itself will block the request and you cannot handle/modify/forward the request to something else which can handle such requests. (only solution is to have another resource infront of your apim...)

An example of an invalid API: https://<yourapim>.azure-api.net/<yourapi>/635f3756574947646a666f3a415041393162457967646b716b78445f64707358526c4c6c7a313835655371527746644c467931587053614273583763584377644e6367356c62694a78466f6176565f7944764c2d63413164484e4b5a36413455714d52454b6e4e51384f4c687a687a6c654c553537374a467566534b6e636b46534d3

22 votes
Vote
Sign in
(thinking…)
Sign in with: Microsoft
Signed in as (Sign out)
You have left! (?) (thinking…)
Sebastian Schöbinger shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

1 comment

Sign in
(thinking…)
Sign in with: Microsoft
Signed in as (Sign out)
Submitting...
  • O'Hare, Ryan commented  ·   ·  Flag as inappropriate

    +3 votes...we have several applications which were not designed by us that have this issue with path parameters over 260 characters (I personally think this is not a great design, but we are bound by how the 3rd party application functions)

Feedback and Knowledge Base