Verified against current HEAD as well as most recent release.
go version weekly.2012-03-27 +10a3b26f9276
What steps will reproduce the problem?
If possible, include a link to a program on play.golang.org.
1. run this test server (port 8000) http://play.golang.org/p/OeqWgVIXUT (Doesn't work on
play.golang.org)
2. run ab -n 1 -c 1 'https://localhost:8000/'
3. Observe failure.
What is the expected output?
ab (apache bench) should print out a message stating that there was 1 Complete Request
and 0 Failed requests.
What do you see instead?
ab prints out a message stating that there was 1 Complete request and 1 Failed request.
Additionally, there is an SSL error:
Benchmarking localhost (be patient)...SSL read failed - closing connection
140518402995936:error:140943E8:SSL
routines:SSL3_READ_BYTES:reason(1000):s3_pkt.c:1247:SSL alert number 0
Which compiler are you using (5g, 6g, 8g, gccgo)?
Standard go run $file on amd64. I believe 6g is the default?
Which operating system are you using?
Ubuntu 12.04 amd64.
Which version are you using? (run 'go version')
Verified on both current go version and HEAD: go version weekly.2012-03-27 +10a3b26f9276
Please provide any additional information below.
I've attatched an export from wireshark below. This server works fine with curl. SSL
negotiation seems to happen perfectly, but there is some problem on teardown. I don't
believe this is the same as the issue recently closed that affects 1/256 connections.
Attachments:
- bad_ssl_server.go (609 bytes)
Attachments: