b00tsy
b00tsy
same problem here
The native node `crypto` module got quite powerful in recent releases, meaning no dependencies at all would be required anymore. However, it would break support for previous node versions (probably...
I use some fancy Alamofire features, such as tls certificate pinning, Timeline (connection latency) and retry strategies in poor connection circumstances, so I'd prefer to stick with Alamofire...
Cool, thanks. The performance issue you pointed out probably is an important issue of which I have no experience, yet. Would be bad if that unnecessarily increased the time an...
So you had some closing thoughts on the issue?
Excellent, thanks! Yeah that example was not the best solution around...
That's the low level implementation where every user wanting to use client certificates would have to modify the code of socket.io-client-swift, which is a good starting point to get it...
strange, client certificate auth was once added, but seems to have disappeared again: https://github.com/daltoniam/Starscream/pull/481 client certificate authentication was silently removed in v4: https://github.com/daltoniam/Starscream/pull/653/files
I also think `GPSLocationOptions` needs a second parameter distinguishing between `desiredAccuracy` of `CLLocationManager` and the filter that is being applied on the data in `GPSLocationRequest.validateData`. The intention of `desiredAccuracy` in...
Full error message: ``` { "notice": "seneca: Action failed: Response Error: 500 Internal Server Error.", "code": "act_execute", "err": { "data": { "isResponseError": true, "headers": { "content-type": "application/json", "cache-control": "private, max-age=0,...