| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
| |
BUG=118398
TEST=\*Reset\*WithTransferEncoding
Review URL: http://codereview.chromium.org/9836050
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@129136 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
ChromeOS file manager cannot handle non NFC encoded utf8 file names (because of
file path normalization done in webkit layer), so let's ensure we normalize
downloaded file names.
BUG=chromium-os:26028
TEST=downloaded file with nfd encoded names and made sure they can be handled by file manager
Review URL: https://chromiumcodereview.appspot.com/9854011
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@129128 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
SocketStream should hold its state as next_state_ before suspending with
ERR_IO_PENDING. This information is required to resume the state machine.
BUG=119793, 53836
TEST=manual test with TLS-enabled pywebsocket console page
Review URL: http://codereview.chromium.org/9809019
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@129106 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
| |
BUG=None
Review URL: http://codereview.chromium.org/9834031
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@129078 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
MessageLoop with orphaned tasks.
This change maintains the same API promises*, but instead of orphaning tasks when they are stopped, the BaseTimer_Helper class holds on to the task until either (1) it expires or (2) the user requests a delay that would arrive earlier than the pending task. If the user requests a longer delay than the pending task, a followup task will be posted when the pending task fires to span the remaining time.
* The one change of usage is related to threading. The threading requirements are now more strict. It is not allowed to destruct a timer on a different thread than the one used to post tasks. A thread ID DCHECK is now in place that will help catch misuse. Some existing instances are changed as part of this CL.
A side effect of this change is that the BaseTimer and DelayTimer are simplified to use features of BaseTimer_Helper (which is now called Timer).
As suggested in timer.h, I ran the disabled TimerTest tests from linux, and they pass consistently. I also added some new tests to verify correct run states.
BUG=117451,103667,119714,119750
Committed: http://src.chromium.org/viewvc/chrome?view=rev&revision=128412
Reverted: http://src.chromium.org/viewvc/chrome?view=rev&revision=128506
Review URL: https://chromiumcodereview.appspot.com/9655006
TBR=jbates@chromium.org
Review URL: https://chromiumcodereview.appspot.com/9791009
TBR=aa@chromium.org
Review URL: https://chromiumcodereview.appspot.com/9860014
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@129062 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Revert 127893 -Revert 127730 - Revert 127717 - Revert 118788 - Revert 113405 - Revert 113305 - Revert 113300 - Revert 112134 - Revert 112130 - Close idle connections / SPDY sessions when needed
Due to the idle connection state being held by different socket pools, it's possible for one socket pool to hold an idle socket in a lower layer socket pool. From the lower level socket pool's perspective, the socket is being "actively" used. From the higher socket pool's (including SpdySession, which is more of a connection manager) perspective, the connection is idle and can be closed if we have hit a limit.
Normally this isn't a big deal, except when we have a lot of idle SPDY connections and are connecting via a proxy, so we have low connection limits through the proxy server. We address this problem by allowing lower-level socket pools to tell higher level socket pools to close a socket.
Fixed ASAN test failures by removing .Times(1) and .Times(2) from CloseMultipleIdleSocketsHeldByLayeredPoolWhenNeeded unittest (this removes the tests relying on the order of std::set in CloseOneIdleConnectionInLayeredPool). ASAN is prob
ably causing the memory allocator to allocate the pools differently. The std::set is ordered by LayeredPool* which is the address of the LayeredPool (willchan).
Added NET_EXPORT for layered_pool class defintion to fix windows shared compile.
BUG=62364, 92244, 109876, 110368, 119847
TEST=
Review URL: http://codereview.chromium.org/9809033
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@129034 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
orphaned tasks.
This change maintains the same API promises*, but instead of orphaning tasks when they are stopped, the BaseTimer_Helper class holds on to the task until either (1) it expires or (2) the user requests a delay that would arrive earlier than the pending task. If the user requests a longer delay than the pending task, a followup task will be posted when the pending task fires to span the remaining time.
* The one change of usage is related to threading. The threading requirements are now more strict. It is not allowed to destruct a timer on a different thread than the one used to post tasks. A thread ID DCHECK is now in place that will help catch misuse. Some existing instances are changed as part of this CL.
A side effect of this change is that the BaseTimer and DelayTimer are simplified to use features of BaseTimer_Helper (which is now called Timer).
As suggested in timer.h, I ran the disabled TimerTest tests from linux, and they pass consistently. I also added some new tests to verify correct run states.
BUG=117451,103667,119714,119750
Committed: http://src.chromium.org/viewvc/chrome?view=rev&revision=128412
Reverted: http://src.chromium.org/viewvc/chrome?view=rev&revision=128506
Review URL: https://chromiumcodereview.appspot.com/9655006
TBR=jbates@chromium.org
Review URL: https://chromiumcodereview.appspot.com/9791009
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@129018 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This change maintains the same API promises*, but instead of orphaning tasks when they are stopped, the BaseTimer_Helper class holds on to the task until either (1) it expires or (2) the user requests a delay that would arrive earlier than the pending task. If the user requests a longer delay than the pending task, a followup task will be posted when the pending task fires to span the remaining time.
* The one change of usage is related to threading. The threading requirements are now more strict. It is not allowed to destruct a timer on a different thread than the one used to post tasks. A thread ID DCHECK is now in place that will help catch misuse. Some existing instances are changed as part of this CL.
A side effect of this change is that the BaseTimer and DelayTimer are simplified to use features of BaseTimer_Helper (which is now called Timer).
As suggested in timer.h, I ran the disabled TimerTest tests from linux, and they pass consistently. I also added some new tests to verify correct run states.
BUG=117451,103667,119714,119750
Committed: http://src.chromium.org/viewvc/chrome?view=rev&revision=128412
Reverted: http://src.chromium.org/viewvc/chrome?view=rev&revision=128506
Review URL: https://chromiumcodereview.appspot.com/9655006
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@128993 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
| |
This change merges some > 80-char lines together. hsts_preloaded.h is a
dummy file to make a future CL easier to review.
(Not reviewed)
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@128985 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
| |
This CL is the result of:
% cat public_key_hashes.h transport_security_state.cc > hsts_preloaded.h
This is purely to make a future CL easier to review.
(Not reviewed)
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@128984 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
| |
The experiment is over, let's get rid of the (big) histogram.
BUG=None
Review URL: http://codereview.chromium.org/9826043
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@128831 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
| |
BUG=114484
TEST=existing filesystem tests don't break
Review URL: https://chromiumcodereview.appspot.com/7811006
TBR=ericu@google.com
Review URL: https://chromiumcodereview.appspot.com/9808101
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@128757 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
| |
BUG=114484
TEST=existing filesystem tests don't break
Review URL: https://chromiumcodereview.appspot.com/7811006
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@128753 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
| |
specified stream_id is not active.
BUG=116825
Review URL: http://codereview.chromium.org/9808083
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@128747 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
HttpServerProperties stores SPDY settings in SettingsMap
whose key is settings ID and value is a (flags, value)
pair (SettingsFlagsAndValue).
The format of the persisted data is same as before (restored
the old code that persisted the data). Verified it with an older
version of the Preferences file that is very large. Verified
that we have sent the right data (sorted and unique settings)
to the server and that duplicates were removed from the file.
Changed all the code above SpdyFramer to use the above
spdy::SettingsMap and spdy::SettingsFlagsAndValue
data structures.
When chrome sends Spdy Settings to the server, it uses
the current SpdyFramer's API calls to create Settings
frame.
TODO:
1) Delete spdy::SpdySettings and spdy::SpdySetting
and replace them with SettingsMap, SpdySettingsIds,
SpdySettingsFlags and value.
2) Add version to the persisted data.
BUG=117760
R=rch, willchan
TEST=network unit tests and browser unit tests.
Review URL: http://codereview.chromium.org/9802003
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@128737 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
| |
BUG=119604
Review URL: http://codereview.chromium.org/9839027
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@128720 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
| |
BUG=107413
TEST=Run with --enable-async-dns on Windows. Experience no firewall warning.
Review URL: http://codereview.chromium.org/9836041
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@128713 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
| |
BUG=106103
TEST=SpdyCredentialStateTest.*,SpdyFramerTest.*Credential*,SpdyHttpStreamTest.*Credential*,SpdySessionTest.*Credential*
Review URL: http://codereview.chromium.org/9535019
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@128707 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Many of the updates a sync client receives are echoes of its own
changes. This patch attempts to count how often these updates are
received by comparing the version of downloaded updates against the
local version.
These counts are exposed locally through AllStatus/about:sync. We also
upload this information to the server through the ClientDebugInfo
mechanism.
BUG=117565
TEST=
Review URL: http://codereview.chromium.org/9702083
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@128659 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
| |
1. maximum_backoff_ms and entry_lifetime_ms now are int64.
2. Protection from integer overflow when calculating delay.
Review URL: https://chromiumcodereview.appspot.com/9838069
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@128617 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
I'm interested in InFlightIO::io_list_, which is of type
std::set<scoped_refptr<BackgroundIO> >, so it holds refs to the
underlying objects.
On the primary/callback thread, the erase call in
InFlightIO::InvokeCallback can delete the operation if the list holds
the last reference. This typically can't happen because the pending
tasks hold a reference to the operation; this is good: it means that
operations are deleted/newed on the background thread, I believe.
This DCHECK() is useful for when you make changes that can delete an
operation in the primary thread, like we found with some of the posix
races in http://codereview.chromium.org/9702059/
Question: for debugging I like the use of scoped_refptr<BackgroundIO>;
but since we never want to delete here, wouldn't a set<BackgroundIO*>
on non-debug builds be more in line with our use?
BUG=None
Review URL: http://codereview.chromium.org/9758002
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@128593 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
| |
No real code change.
BUG=none
TEST=none
Review URL: https://chromiumcodereview.appspot.com/9839040
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@128540 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
tasks."
This reverts commit r128412, which is causing DCHECKs in thread
destruction in media unittests.
BUG=119714,119750
TBR=sky@chromium.org,petermayo@chromium.org
Review URL: https://chromiumcodereview.appspot.com/9839059
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@128506 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
| |
Also adds hostname normalization to lower case when resolving from HOSTS.
BUG=112907, 118412, 118995
TEST=./net_unittests --gtest_filter=DnsConfigService*
Review URL: http://codereview.chromium.org/9721002
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@128498 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
| |
BUG=chromium-os:28062
TEST=Send more bits with --enterprise-enrollment-initial-modulus than the server expects. AE still succeeds.
Review URL: http://codereview.chromium.org/9835021
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@128475 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
about:flags.
Added command line switches --enable-spdy3 to enable
SPDY/3 and --enable-spdy-flow-control to enable flow control (SPDY/2.1).
Added Field Trials for SPDY/2.1 and SPDY/3. The FieldTrials are enabled
when SPDY/3 and flow control command line options are not chosen.
Removed --use-spdy=v3 and --use-spdy=flow-control options.
BUG=118440,119205
R=willchan
TEST=Netowrk unit tests and browser tests.
Enable SPDY/3 in about:flags and see in chrome://net-internals
that SPDY/2, SPDY/2.1 and SPDY/3 are displayed as the protocols
supported.
Enable SPDY FLow Control in about:flags and see in chrome://net-internals
that SPDY/2 and SPDY/2.1 are displayed as the protocols supported.
Review URL: http://codereview.chromium.org/9766021
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@128420 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The on-demand OCSP test server is not supported on Android. Disable
these tests.
BUG=119642
TEST=green bots
Review URL: http://codereview.chromium.org/9837027
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@128414 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This change maintains the same API promises*, but instead of orphaning tasks when they are stopped, the BaseTimer_Helper class holds on to the task until either (1) it expires or (2) the user requests a delay that would arrive earlier than the pending task. If the user requests a longer delay than the pending task, a followup task will be posted when the pending task fires to span the remaining time.
* The one change of usage is related to threading. The threading requirements are now more strict. It is not allowed to destruct a timer on a different thread than the one used to post tasks. A thread ID DCHECK is now in place that will help catch misuse. Some existing instances are changed as part of this CL.
A side effect of this change is that the BaseTimer and DelayTimer are simplified to use features of BaseTimer_Helper (which is now called Timer).
As suggested in timer.h, I ran the disabled TimerTest tests from linux, and they pass consistently. I also added some new tests to verify correct run states.
BUG=117451,103667
Review URL: http://codereview.chromium.org/9655006
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@128412 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
| |
in SYN_STREAM.
Add credential_slot to BufferedSpdyFramer::CreateSynStream
Review URL: http://codereview.chromium.org/9839013
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@128382 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
| |
spdy_framer.cc to be consisten with style.
Review URL: http://codereview.chromium.org/9835019
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@128375 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
| |
No real code change.
BUG=none
TEST=none
Review URL: https://chromiumcodereview.appspot.com/9812031
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@128364 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
| |
BUG=115348
TEST=try bots
Review URL: https://chromiumcodereview.appspot.com/9814028
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@128323 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
| |
Review URL: http://codereview.chromium.org/9815028
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@128310 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
| |
and address parse result.
BUG=114833, 117770
TEST=Find AsyncDNS.Result in chrome://histograms
Review URL: http://codereview.chromium.org/9794001
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@128280 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
| |
For device_management.py only
BUG=none
TEST=none
Review URL: http://codereview.chromium.org/9839002
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@128256 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
| |
R=mnissler@chromium.org
BUG=none
TEST=none
Review URL: http://codereview.chromium.org/9814011
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@128226 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
| |
BUG=83775
Review URL: http://codereview.chromium.org/9819001
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@128196 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
| |
BUG=114343
TEST=goes green
TBR=wtc
Review URL: https://chromiumcodereview.appspot.com/9836001
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@128174 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
With this split, CertVerifyProc is responsible for
interacting with the underlying PKIX path building and
verification library, while X509Certificate is responsible
for parsing certificates with the underlying crypto library
and exposing a common interface for higher-level code such
as UI.
BUG=114343
TEST=net_unittests
Review URL: https://chromiumcodereview.appspot.com/9691054
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@128172 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
| |
Porting changes from server.
BUG=119221
R=rch
TEST=network unit tests
Review URL: https://chromiumcodereview.appspot.com/9814025
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@128169 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
| |
state of a number of SPDY global variables.
Review URL: http://codereview.chromium.org/9817014
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@128163 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
In preparation for moving certificate path building and
verification out of X509Certificate, introduce a
CertVerifierProc that can be used by the
MultiThreadedCertVerifier to verify certificates using the
underlying system store.
Unit tests previously coded against X509Certificate are now
coded against the CertVerifierProc, as future CLs will shift
verification into this interface.
This was originally reviewed as http://codereview.chromium.org/9584041/ and
http://codereview.chromium.org/9553014/ , and has been
combined in order to preserve SVN history.
BUG=114343
TEST=net_unittests
R=wtc
Review URL: https://chromiumcodereview.appspot.com/9812035
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@128150 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
| |
BUG=119293
Review URL: https://chromiumcodereview.appspot.com/9810022
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@128142 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
- Provide render_process_id from RenderProcessHostImpl and WorkerProcessHost
to SocketStreamDispatcherHost.
- Provide render_view_id from SocketStreamHost to SocketStreamDispatcherHost.
- Implement SSLErrorHandler::Delegate in SocketStreamDispatcherHost.
- Then use SSLManager in SocketStreamDispatcherHost.
BUG=53836
TEST=none
Review URL: http://codereview.chromium.org/9704045
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@128093 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The existing CertVerifier implementation has been renamed to
MultiThreadedCertVerifier, consistent with ProxyResolver naming.
This is patch 1 of N for http://crbug.com/114343
BUG=114343
TEST=Compiles and existing unittests pass.
Review URL: https://chromiumcodereview.appspot.com/9476035
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@128090 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This change makes ClientSocketPoolManager aware of SocketPoolType so it can
pick a different limit for normal socket pools and WebSocket socket pools.
As an initial (experimental) setting, number of max sockets per group for
WebSocket connections is raised to 30, and other limits are set to the same
value as normal socket pools. This configuration should be revisited later
when WebSocket protocol stack starts to work and a good amount of usage metrics
are collected.
BUG=118268
TEST=none
Review URL: http://codereview.chromium.org/9764003
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@128044 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
| |
Content-Disposition headers.
R=willchan@chromium.org
BUG=103618
Review URL: http://codereview.chromium.org/9757002
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@128041 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This CL seems to have broken the Win & Win Aura builds.
I reused the Comodo certificate since it's valid for > year and it's the
last one that I touched.
BUG=111893
TEST=net_unittests
TBR=agl@chromium.org
Review URL: https://chromiumcodereview.appspot.com/9815015
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@127993 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
| |
I reused the Comodo certificate since it's valid for > year and it's the
last one that I touched.
BUG=111893
TEST=net_unittests
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@127988 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
| |
BUG=chromium-os:14021
TEST=Manually. There whould be no error on opening file:///home/chronos/user/log in chrome on chromeos.
Review URL: http://codereview.chromium.org/9699021
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@127961 0039d316-1c4b-4281-b951-d872f2087c98
|