Closed osiloke closed 8 years ago
Sure, this should be a relatively easy fix. Do you speak about headers per client (TusClient#setHeaders
), per upload (TusUpload#setHeaders
) or both in your case? Since I see use cases for all situations, I guess we need both.
so i think both cases are helpful at least for flexibility... TusUploader#setheader, TusClient#setHeader
Currently sitting on implementing this feature. Expect it soon!
The 0.3.0
release includes this feature.
This will allow authorization headers. I know authorization is not part of the protocol, but the protocol documentation suggest that you should perform authorization via additional headers. The current api does not allow this.