Headless Chrome doesn't initialize the IOThread for AIA fetching |
|||||
Issue descriptionWhen running Headless Chrome with NSS certs, Headless does not initialize the IOThread for use with AIA fetching. //chrome/browser/io_thread.cc does so via https://cs.chromium.org/chromium/src/chrome/browser/io_thread.cc?rcl=78cb52909f06fe32e6a71da39f229941e0fba697&l=439 , ensuring that the Chrome IOThread will be used to handle network fetches.
,
Aug 13 2017
Thanks for the report! I'm wondering if this can be the cause of some cert errors people have been reporting, e.g. https://crbug.com/751032
,
Aug 14 2017
,
Aug 14 2017
That wouldn't/shouldn't be related (auth != certs), but was prompted from an internal thread about certificate errors (for a misconfigured server) :)
,
Aug 15 2017
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/00b4dabf83be8cb54213ea6cf66957699be3f539 commit 00b4dabf83be8cb54213ea6cf66957699be3f539 Author: David Vallet <dvallet@chromium.org> Date: Tue Aug 15 23:49:55 2017 Initialize IOThread for AIA fetching in headless Bug: 754319 Change-Id: Iec5cebdfa53916bf8759909e444bafdc7acf5881 Reviewed-on: https://chromium-review.googlesource.com/611695 Reviewed-by: David Vallet <dvallet@chromium.org> Reviewed-by: Sami Kyöstilä <skyostil@chromium.org> Commit-Queue: David Vallet <dvallet@chromium.org> Cr-Commit-Position: refs/heads/master@{#494610} [modify] https://crrev.com/00b4dabf83be8cb54213ea6cf66957699be3f539/headless/lib/browser/headless_browser_impl.cc
,
Aug 16 2017
,
Aug 16 2017
|
|||||
►
Sign in to add a comment |
|||||
Comment 1 by eseckler@chromium.org
, Aug 10 2017Status: Available (was: Untriaged)