aboutsummaryrefslogtreecommitdiffstats
path: root/org.eclipse.jgit.test/.settings
diff options
context:
space:
mode:
authorShawn Pearce <spearce@spearce.org>2016-07-05 13:05:04 -0700
committerShawn Pearce <spearce@spearce.org>2016-07-05 17:22:37 -0700
commit63cf87f8630e1176008f308742d7a72f5c7ec123 (patch)
tree3d525f304892d3f15e95385c030a212dae3a5b10 /org.eclipse.jgit.test/.settings
parenta1bedf08228350733a6dd9c2c8c0c9053efbbcec (diff)
downloadjgit-63cf87f8630e1176008f308742d7a72f5c7ec123.tar.gz
jgit-63cf87f8630e1176008f308742d7a72f5c7ec123.zip
ReceivePack: report protocol parsing failures on channel 3
If the client sent a well-formed enough request to see it wants to use side-band-64k for status reporting (meaning its a modern client), but any other command record was somehow invalid (e.g. corrupt SHA-1) report the parsing exception using channel 3. This allows clients to see the failure and know the server will not be continuing. git-core and JGit clients send all commands and then start a sideband demux before sending the pack. By consuming all commands first we get the client into a state where it can see and respond to the channel 3 server failure. This behavior is useful on HTTPS connections when the client is buggy and sent a corrupt command, but still managed to request side-band-64k in the first line. Change-Id: If385b91ceb9f024ccae2d1645caf15bc6b206130
Diffstat (limited to 'org.eclipse.jgit.test/.settings')
0 files changed, 0 insertions, 0 deletions