webclient | Angular webclient | Email library

I have one big question here. While this is correct (it yields the same response) is this the correct thing to do?

Essentially, yes, you've done it correctly. The only things that aren't really correct there are your Webclient usage, and your style.

You certainly don't have to specify a WebClient per URI (and you shouldn't, they're meant to be reusable.) So if you have different domains and the same webclient, just create a standard instance:

This problem can be solved with the method exchangeToMono. This results into the following snippet.

This creates a single webClient, no matter how many of the component you render:

By default WebClient runs with a connection pool. The default settings for the pool are 500 max connections and max 1000 pending requests. You have JMeter and try to simulate 10000 but you do not specify how you distribute the load. You may need to increase the max pending requests. Have a look at this documentation and this documentation.

If you want to configure the WebClient then you need:

There are various implementations you could do here for control flow (I think @jimi's comments on using DialogResult is a decent approach), but what's important is that you should not attempt to do a nested Application.Run call.

In this implementation, we'll close Loading Form which will continue the execution in Main. Note that doing Application.Exit also will continue execution in Main, but it won't actually Run any new forms. As such, you do have a scenario where we can add that behavior (whether or not you actually intended to have this behavior is up to your requirements).

if you want to get file name from url:

There is a bug in ForkTsCheckerWebpackPlugin create-react-app (CRA) uses. Updating it to the latest version (at the time of writing 6.2.10) and using this CRA override solves the issue:

Log4J has multiple appenders, one of which is HTTP Appender.

https://logging.apache.org/log4j/2.x/manual/appenders.html#HttpAppender

See requirements and example below:

HttpAppender

The HttpAppender sends log events over HTTP. A Layout must be provided to format the LogEvent.

Will set the Content-Type header according to the layout. Additional headers can be specified with embedded Property elements.

Will wait for response from server, and throw error if no 2xx response is received.

Here is a sample HttpAppender configuration snippet:

This works so you're probably not getting a ViewModel back from your webClient body but rather the map of parameters (or something) from the ViewModel.