Jon Shier

While it's unlikely we'd actually support the NEL standard (it's complex and seems to be of rather limited utility), an analysis of what would be need for support outside Alamofire...

Probably not. Enabling it as an external library would be our goal.

Path encoding is something we've been trying to find an elegant solution for for years now, without success. The solution you've outlined has been considered, but it's fragile, inflexible, and...

I've recently started using Vapor for some backend work and they have a [`PathComponents`](https://github.com/vapor/routing-kit/blob/master/Sources/RoutingKit/PathComponent.swift) type which may be a useful approach here, though it would be a rather significant addition...

There is no equivalent in Alamofire, as it does not use streams for uploads. It's unlikely we'd ever add support for this, but what's your use case?

You can get the same functionality by creating your own `OutputStream` with the appropriate settings, which you then use with `upload` directly. If you need multipart encoding, you'd have to...

Good point. This needs a bit more investigation.

We've discussed adding SPKI support in the past. However, due to the complexity of the feature we decided not to merge the existing PR. Instead, we feel that the feature...

To be clear, there wasn't necessarily anything wrong with the original PR. It's just that, given the risks involved, we decided we should build the feature ourselves. We can't really...

@tronthomas Currently the `cURLDescription` method is rather ad hoc, as it has evolved alongside the library over the years. It would be great if it we could better define exactly...