summaryrefslogtreecommitdiff
path: root/include/git2
diff options
context:
space:
mode:
authorSven Strickroth <email@cs-ware.de>2020-09-08 13:03:07 +0200
committerSven Strickroth <email@cs-ware.de>2020-09-08 13:03:07 +0200
commit2dea3eb41a8e75eea464b3d1bcdffcf0530f4cbc (patch)
treed260a86e14dc2879fa91a70b22f75a275e48ff6f /include/git2
parentf29e6ddec179726d0879c9b4a86a87f897766833 (diff)
downloadlibgit2-2dea3eb41a8e75eea464b3d1bcdffcf0530f4cbc.tar.gz
Don't fail if a HTTP server announces he supports a protocol upgrade
cf. RFC7230 section 6.7, an Upgrade header in a normal response merely informs the client that the server supports upgrading to other protocols, and the client can ask for such an upgrade in a later request. The server requiring an upgrade is via the 426 Upgrade Required response code, not the mere presence of the Upgrade response header. (closes issue #5573) Signed-off-by: Sven Strickroth <email@cs-ware.de>
Diffstat (limited to 'include/git2')
0 files changed, 0 insertions, 0 deletions