Errors in OpenApiDocument.FromUrlAsync when the web server requires a user-agent

I’m trying to generate a client for a government API that has their server configured to reject requests that do not specify a User-Agent header. This seems like an odd thing to do, but I guess they are trying to track usage or detect abuse via that header.

Our workaround is to download the spec and generate from a file, but it would be nice to not need that.

I think we could fix this by specifying a header in DynamicApis before we make the request, but I’m unclear why we use DynamicApis instead of HttpClient directly.

[jeremyVignelles]

Not sure there is something to add here in NSwag. If an option was introduced for setting the user agent, then others wouldn’t understand :

• why the header X is not allowed
• why basic authentication is not supported…
• why they can’t contact a website with a self-signed certificate

I’d argue to keep the project and options simple, and for complex scenarios like these, download the file with a curl, a dotnet-script, a console app or whatever, and pass that file to NSwag.

[ryepup]

Closing this out, there are options to solve the problem outside nswag and all the proposed solutions open up pandora’s box to endless scope/feature creep.

Thanks for consideration @RicoSuter and for the great counterpoint @jeremyVignelles.