Closed cristianbotiza closed 1 year ago
Hi, thanks for your contribution! If you haven't already done so, could you please make sure you sign our CLA (https://jitsi.org/icla for individuals and https://jitsi.org/ccla for corporations)? We would unfortunately be unable to merge your patch unless we have that piece :(.
Merging #495 (eeec10c) into master (7ab9aa2) will not change coverage. The diff coverage is
0.00%
.
Nice catch, that's a sneaky one.
Previous fix has slightly refactored the handling of the JWT header, thereby introducing a regression. https://community.jitsi.org/t/jibri-is-not-sending-webhook-authorization-header/117184/
When passing the defaultRequest closure we must ensure we supply a block that forces re-evaluation of the
jwt
property, subsequently executing the expiry check in RefreshingProperty. As such,$jwt
is valid, while$it
is not, becauseit
is resolved only once, when the Client is setup. Whatever value is computed then, is seen as a constant when passed to defaultRequest.$jwt
, on the other hand, forces re-evaluation every time the default request block is executed, i.e. for every webhook request.