2 replies

Clarification on Handling Security in `HttpApiClient`

do I understand correctly that now to work with security in the

HttpApiClient

HttpApiClient

, it is proposed to transform the client - for example, to provide tokens? Are there any plans to make the work with security more explicit? for example, in

effect-http

effect-http

, it was necessary to provide tokens explicitly with each call to a secure endpoint. in the current implementation, perhaps it is necessary to treat the missing security-credentials as dependencies and reflect this in the

channel?

Clarification on Handling Security in `HttpApiClient`

Similar Threads

Clarification on Handling Security in `HttpApiClient`

Similar Threads

Similar Threads

Similar Threads