Configuring requests for non-fully-OpenAPI-compliant APIs

[Guillermo López-Anglada (guillermooo)]

I guess the correct answer here is to ensure the server follows the OpenAPI spec to the letter, but often that's unrealistic.

For example, Kiota url-encodes path parameters. Hypothetical Web API Acme provides the /list/directory/{dirPath} resource and accepts only non-url-encoded dirPaths that must end in /. I don't think a Kiota client can be easily configured to disable url-encoding in requests to said resource? I'd like to send the request /list/directory/somePath/, but Kiota always sends /list/directory/somePath%2f.

I've found workarounds, like using a rawUrl with the relevant request builder, and patching the generated code. However, it seems Kiota should accept the fact that APIs out there are going to be imperfect and allow some configuration points.

Maybe I've missed that Kiota already provides this kind of flexibility?

[Guillermo López-Anglada (guillermooo)]

I suppose I can answer myself by pointing to middleware.