Tree

Tree:
45a38d9c26a3dde7dfa3be4bc0032d3afb569b6f
Date:
Message:
client: Fix content type check in AbstractHttpGitClient._smart_request Some git servers can send a Content-Type header containing a charset directive. Official git client can successfully clone repositories hosted on such server but dulwich was raising a GitProtocolError as the code to check the header value was not expecting a directive to be present in it.
.codespellrccommits | blame
.coveragerccommits | blame
.deepsource.tomlcommits | blame
.flake8commits | blame
.github/
.gitignorecommits | blame
.mailmapcommits | blame
.readthedocs.ymlcommits | blame
.stestr.confcommits | blame
.testr.confcommits | blame
AUTHORScommits | blame
CODE_OF_CONDUCT.mdcommits | blame
CONTRIBUTING.rstcommits | blame
COPYINGcommits | blame
MANIFEST.incommits | blame
Makefilecommits | blame
NEWScommits | blame
README.rstcommits | blame
SECURITY.mdcommits | blame
TODOcommits | blame
bin/
devscripts/
disperse.confcommits | blame
docs/
dulwich/
dulwich.cfgcommits | blame
examples/
pyproject.tomlcommits | blame
requirements.txtcommits | blame
setup.py*commits | blame
status.yamlcommits | blame
testdata/
tox.inicommits | blame