You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the BaseServicesStrategy and the OTEServiceClient, the default headers for e.g. the content-type are set while retrieving the headers from the private attributes of the respective class. The code is partially repetetive and needs to be cleaned.
(See here and here)
The text was updated successfully, but these errors were encountered:
So looking into this and thinking about it, I don't see how we can do it otherwise.
The client (OTEServiceClient) sets the headers in each created strategy from its own headers (at the time of creation), but from there on its impossible for client to have any more control over what headers are used for the specific strategy to do its calls. And I think that's as it should be.
While these calls are indeed sent to the same OTE Service, there may be a desire to not replicate certain headers more than necessary, as well as carrying through headers into transformations or other kind of calls the OTE Service might perform further along?
In either case, it feel "right" to me that there are no "globally set" headers for an instantiated client and its created strategies, but rather than the strategies' headers reflect the headers set in the client at creation.
In the
BaseServicesStrategy
and theOTEServiceClient
, the default headers for e.g. the content-type are set while retrieving the headers from the private attributes of the respective class. The code is partially repetetive and needs to be cleaned.(See here and here)
The text was updated successfully, but these errors were encountered: