net/testserver.py: Add handler to reply with client auth status.

net/testserver.py: Add handler to reply with client auth status.

BUG=514575
Committed: https://crrev.com/1300c883029570b4ab83ac12e340e9500e54c7e3
Cr-Commit-Position: refs/heads/master@{#342337}

[pneubeck (no reviews), 2015-08-06 08:58:47]

pneubeck@chromium.org changed reviewers:
+ rsleevi@chromium.org

[pneubeck (no reviews), 2015-08-06 08:58:47]

separated from the larger CL.
ptal

[pneubeck (no reviews), 2015-08-06 09:22:06]

The CQ bit was checked by pneubeck@chromium.org to run a CQ dry run

[commit-bot: I haz the power, 2015-08-06 09:22:23]

Dry run: CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1275853003/1
View timeline at
 https://chromium-cq-status.appspot.com/patch-timeline/1275853003/1

[commit-bot: I haz the power, 2015-08-06 09:30:15]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2015-08-06 09:30:16]

Dry run: This issue passed the CQ dry run.

[Ryan Sleevi, 2015-08-06 23:48:52]

Pre-emptive LGTM, but I have a design suggestion change for how you're
signalling the client cert. While not immediately necessary, I expect the moment
you start writing tests for this, I'll ask for this functionality :)

https://codereview.chromium.org/1275853003/diff/1/net/tools/testserver/testse...
File net/tools/testserver/testserver.py (right):

https://codereview.chromium.org/1275853003/diff/1/net/tools/testserver/testse...
net/tools/testserver/testserver.py:1530: self.wfile.write('got no client cert')
nit: Would it make more sense to write the SHA-256 hash of the certificate
chain, as received? That way you can make sure you're getting the _right_ client
cert, consistently :)

[pneubeck (no reviews), 2015-08-07 11:47:42]

https://codereview.chromium.org/1275853003/diff/1/net/tools/testserver/testse...
File net/tools/testserver/testserver.py (right):

https://codereview.chromium.org/1275853003/diff/1/net/tools/testserver/testse...
net/tools/testserver/testserver.py:1530: self.wfile.write('got no client cert')
On 2015/08/06 23:48:52, Ryan Sleevi wrote:
> nit: Would it make more sense to write the SHA-256 hash of the certificate
> chain, as received? That way you can make sure you're getting the _right_
client
> cert, consistently :)

Done.

[pneubeck (no reviews), 2015-08-07 11:47:46]

The CQ bit was checked by pneubeck@chromium.org

[pneubeck (no reviews), 2015-08-07 11:47:47]

The patchset sent to the CQ was uploaded after l-g-t-m from rsleevi@chromium.org
Link to the patchset: https://codereview.chromium.org/1275853003/#ps20001
(title: "Reply with certificate fingerprint.")

[commit-bot: I haz the power, 2015-08-07 11:48:00]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1275853003/20001
View timeline at
 https://chromium-cq-status.appspot.com/patch-timeline/1275853003/20001

[commit-bot: I haz the power, 2015-08-07 11:55:18]

Committed patchset #2 (id:20001)

[commit-bot: I haz the power, 2015-08-07 11:56:01]

Patchset 2 (id:??) landed as
https://crrev.com/1300c883029570b4ab83ac12e340e9500e54c7e3
Cr-Commit-Position: refs/heads/master@{#342337}