--
You received this message because you are subscribed to the Google Groups "headless-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to headless-dev+unsubscribe@chromium.org.
To post to this group, send email to headle...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/headless-dev/46329e78-51ca-4078-a49b-e64a56ebc4ed%40chromium.org.
Well, it works fine on a "regular" chrome. This only manifests in headless.
On 18 October 2016 at 17:45, Alex Clarke <alexc...@google.com> wrote:
I'm afraid that's outside of my area of expertise. I'd suggest asking on chromium-dev@ since network folks will be listening there.
On 18 October 2016 at 16:33, 'Alex Vaghin' via headless-dev <headle...@chromium.org> wrote:
Friendly ping.
On Wednesday, 5 October 2016 09:02:20 UTC+2, Alex Vaghin wrote:I get "unknown" SecurityState when inspecting a page using remote debugger protocol:{ explanations: [],insecureContentStatus:{ displayedContentWithCertErrors: false,displayedInsecureContentStyle: 'unknown',displayedMixedContent: false,ranContentWithCertErrors: false,ranInsecureContentStyle: 'unknown',ranMixedContent: false },schemeIsCryptographic: false,securityState: 'unknown' }The page I tried it on was https://airhorner.com but the same result is observed on any TLS-enabled site.Is it expected or a known issue?Also, found the following which may be related or the same thing even:
--
You received this message because you are subscribed to the Google Groups "headless-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to headless-dev...@chromium.org.
To post to this group, send email to headle...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/headless-dev/46329e78-51ca-4078-a49b-e64a56ebc4ed%40chromium.org.
--
You received this message because you are subscribed to the Google Groups "headless-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to headless-dev...@chromium.org.
To post to this group, send email to headle...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/headless-dev/CA%2BV-rCkWkoi%3DwODQ5TObbc%3Dwt1519NRfhi9pEoCa2R7YhmC-8g%40mail.gmail.com.
The DevTools Security domain should now work as intended for headless chrome. If there are any further problems, feel free to reopen this bug.