HTTP/2 [https://http2.github.io] is a major revision of the HTTP protocol focused on performance and efficiency. We are working on enabling HTTP/2 support on the client-facing side of the gateway. Support on the backend-facing will be added later and tracked in a separate roadmap item.

I got a use case to set up interface with SAP ARIBA which is requesting MTOM support . based on the documentation I got I saw the following MTOM - Services using MTOM may work. Official support is not offered at this time.. it was in September 2017 . it should be great to support this feature as ARIBA is becoming a main player in Marketplace area.
Thanks

we publish a set of API exposed through internal services on AKS. Instead of using internal IP Address it would be great to use a sort of hosts file or point API management to a custom dns server so I can publish APIs with hostname and not the IP address.

store the function name that was imported and what end point operations where checked when imported. Then when a new version of the API is created, you can change the function name (would refresh end point operations), and then add/remove (if needed) operations by checkbox. Finally, if a new version of a function is uploaded, an event would fire off to rebuild all the API interfaces that have operations are pointing to it (like when importing) so it can keep in sync with the back end.

Add "display names" properties (of APIs and operations) in Azure Diagnostics log entries. It would permit to make dashboards with a more signifiants labels rather than Ids that were chosed at creation (and that can't be changed after).

I have confirmed with Microsoft support (119010321001270) that if you try and import a v2 function into the APIM gateway where you have overwritten the "routePrefix": "{any thing here but api}" in the host.json file, the backend configuration for that function pointer that APIM sets up is hard coded to "api". So until this fix is implemented, all v2 functions must stay defaulted to "api" for the URL prefix.

I was asked to put this request here so it can be publicly tracked.

We created a microservice using Spring WebFlux (will produce Server Side Events) to expose an API that will publish data as an event stream which is consumed by the client as EventSource. However, the Azure API Gateway is preventing the data to be consumed as text/event-stream.

A similar concern is seen here: https://community.apigee.com/questions/61225/apigee-to-create-a-reactive-rest-api-for-continuou.html