untrusted HTTPS connection reported as successful/undefined in web console

NEW
Unassigned

Status

()

Firefox
Developer Tools: Console
P2
normal
6 years ago
5 years ago

People

(Reporter: Stefan, Unassigned)

Tracking

({sec-want})

Trunk
x86_64
Linux
sec-want
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [net][proxies], URL)

(Reporter)

Description

6 years ago
User Agent:  

Steps to reproduce:

0. (FF should not trust my personal CA/web server)
1. Enable Web Console.
2. Open Testcase.


Actual results:

2. With HTTPS proxy the request of https://www.vogtner.de/mozilla/n/inc.js is tagged "200 Established", without proxy it is "undefined". No cross mark (×).


Expected results:

2. The request shall be tagged as failed (×).
(Reporter)

Updated

6 years ago
(Reporter)

Updated

6 years ago
OS: Other → Linux
Hardware: Other → x86_64

Comment 1

6 years ago
What proxy is running? The issue is the connection is listed as established when connecting through the proxy, correct?

I get 
[13:45:00.970] GET https://www.vogtner.de/mozilla/n/inc.js [undefined 407ms]
(Reporter)

Comment 2

6 years ago
(In reply to Tim (fmdeveloper) from comment #1)
> What proxy is running?

Squid.

> The issue is the connection is listed as established
> when connecting through the proxy, correct?

The issue is that the request does not succeed (whether this is OK is debatable) and that the web console does show the ×-mark in front of the request.

Updated

6 years ago
Component: Untriaged → Developer Tools: Console
QA Contact: untriaged → developer.tools.console
I think we have a problem with the way we're dealing with proxies. Need to take a closer look.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Keywords: sec-want
Whiteboard: [net][proxies]

Updated

5 years ago
Priority: -- → P2
You need to log in before you can comment on or make changes to this bug.