Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(167)

Issue 11478049: Disable SSL session cache to fix issue with SecureSocket connections. (Closed)

Created:
8 years ago by Bill Hesse
Modified:
8 years ago
Reviewers:
Mads Ager (google)
CC:
reviews_dartlang.org
Visibility:
Public.

Description

Disable SSL session cache to fix issue with SecureSocket connections. BUG=dart:7208 TEST=standalone/io/secure_session_resume_test.dart Committed: https://code.google.com/p/dart/source/detail?r=15904

Patch Set 1 #

Total comments: 2

Patch Set 2 : Address comments, speed up test. #

Unified diffs Side-by-side diffs Delta from patch set Stats (+28 lines, -4 lines) Patch
M runtime/bin/secure_socket.cc View 1 chunk +8 lines, -0 lines 0 comments Download
A + tests/standalone/io/secure_session_resume_test.dart View 1 3 chunks +19 lines, -3 lines 0 comments Download
M tests/standalone/standalone.status View 1 1 chunk +1 line, -1 line 0 comments Download

Messages

Total messages: 3 (0 generated)
Bill Hesse
8 years ago (2012-12-10 10:37:31 UTC) #1
Mads Ager (google)
LGTM, but let's make the test as fast as we can. https://codereview.chromium.org/11478049/diff/1/tests/standalone/io/secure_session_resume_test.dart File tests/standalone/io/secure_session_resume_test.dart (right): ...
8 years ago (2012-12-10 11:28:50 UTC) #2
Bill Hesse
8 years ago (2012-12-10 13:13:20 UTC) #3
Made test run faster, added FAIL to status of bad_certificate_test on Windows.

https://codereview.chromium.org/11478049/diff/1/tests/standalone/io/secure_se...
File tests/standalone/io/secure_session_resume_test.dart (right):

https://codereview.chromium.org/11478049/diff/1/tests/standalone/io/secure_se...
tests/standalone/io/secure_session_resume_test.dart:126: int
delay_between_connections = 200;  // Milliseconds.
On 2012/12/10 11:28:50, Mads Ager wrote:
> Does this fail with a smaller timeout as well? Can you delay only one and get
> the issue? We should make this test as fast as we can. Maybe we should make a
> specific test for this issue instead of putting it into the basic test?

The timeout needs to be at least 200 ms, and more if we only do one delayed one.
 I can change it to 400ms, and only do one delayed.  So that is only 500ms for
the entire test.

Powered by Google App Engine
This is Rietveld 408576698