Security state in remote debugger

48 views
Skip to first unread message

Alex Vaghin

unread,
Oct 5, 2016, 3:02:20 AM10/5/16
to headless-dev
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:

Alex Vaghin

unread,
Oct 18, 2016, 11:33:22 AM10/18/16
to headless-dev
Friendly ping.

Alex Clarke

unread,
Oct 18, 2016, 11:45:55 AM10/18/16
to Alex Vaghin, headless-dev
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.

--
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.

Alex Vaghin

unread,
Oct 18, 2016, 11:56:37 AM10/18/16
to Alex Clarke, headless-dev
Well, it works fine on a "regular" chrome. This only manifests in headless.

Eric Seckler

unread,
Oct 24, 2016, 6:41:50 AM10/24/16
to Alex Vaghin, Alex Clarke, headless-dev
Sorry for the delay. We're aware of the issue and have figured out what's causing it. We're tracking things in the bug you linked.

On Tue, Oct 18, 2016 at 4:56 PM 'Alex Vaghin' via headless-dev <headle...@chromium.org> wrote:
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.

--
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.

Eric Seckler

unread,
Nov 17, 2016, 4:03:14 PM11/17/16
to Alex Vaghin, Alex Clarke, headless-dev

The DevTools Security domain should now work as intended for headless chrome. If there are any further problems, feel free to reopen this bug.

Reply all
Reply to author
Forward
0 new messages