mendersoftware / mender-mcu

LAST BUILD ON BRANCH pr_192

branch: pr_192

CHANGE BRANCH

x

Reset

• pr_192
• HEAD
• main
• pr_100
• pr_101
• pr_102
• pr_103
• pr_104
• pr_105
• pr_106
• pr_107
• pr_108
• pr_109
• pr_110
• pr_111
• pr_112
• pr_113
• pr_114
• pr_115
• pr_117
• pr_118
• pr_119
• pr_120
• pr_121
• pr_122
• pr_123
• pr_124
• pr_125
• pr_126
• pr_127
• pr_128
• pr_129
• pr_130
• pr_131
• pr_134
• pr_136
• pr_137
• pr_138
• pr_139
• pr_140
• pr_141
• pr_142
• pr_143
• pr_144
• pr_145
• pr_146
• pr_147
• pr_148
• pr_149
• pr_150
• pr_152
• pr_153
• pr_154
• pr_155
• pr_156
• pr_157
• pr_158
• pr_159
• pr_160
• pr_161
• pr_162
• pr_163
• pr_164
• pr_165
• pr_166
• pr_167
• pr_168
• pr_169
• pr_170
• pr_172
• pr_173
• pr_175
• pr_176
• pr_177
• pr_178
• pr_179
• pr_180
• pr_181
• pr_182
• pr_183
• pr_184
• pr_185
• pr_186
• pr_187
• pr_188
• pr_189
• pr_190
• pr_191
• pr_193
• pr_194
• pr_195
• pr_196
• pr_197
• pr_198
• pr_199
• pr_200
• pr_201
• pr_205
• pr_206
• pr_207
• pr_209
• pr_210
• pr_212
• pr_213
• pr_62
• pr_65
• pr_93
• pr_97
• pr_98
• pr_99
• test-coverage

Build # 1756078223

Build Type

push

gitlab-ci

Committed by vpodzime

Commit Message

chore: Retry HTTP requests in in authenticated_http_perform()

On non-reliable networks (and with the often suboptimal antennas
on MCUs) HTTP requests can quite often fail. In order to not
consider every such failure as an error, we introduce a retry
mechanism (similar to one we already have for DNS resolution).

A low number of attempts (5) together with a short retry interval
(100ms) and a progressive factor (2) for the interval mean that a
real network outage won't cause any extra long delay (1500ms at
most). However, it can handle many issues with network
transparently for the rest of the code.

Since authentication HTTP request can happen as part of
`authenticated_http_perform()` we need to use the retry mechanism
there too. However, if all tries fail, we don't even try the API
HTTP request. In case the very last authentication attempt
succeeds and the very last API request succeeds, the total
execution of `authenticated_http_perform()` can take up to 3
seconds. However, only one such case can happen because the
authentication info (JWT token) is cached.

Ticket: MEN-8223
Changelog: none
Signed-off-by: Vratislav Podzimek <vratislav.podzimek+auto-signed@northern.tech>

Run Details