Bug 1759114 Comment 0 Edit History

Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.

Issue reproduceable in Fenix, Focus and on Desktop.

STRs:
- enable https-only mode
- type in the url bar: `expired.badssl.com` (seems like any subdomains would work in reproducing the issue)

Expected result:
- Engine's `RequestInterceptor`'s `onErrorRequest` fires with ERROR_SECURITY_BAD_CERT
- the error page for "secure connection failed" is shown

Actual result:
- Engine's `RequestInterceptor`'s `onErrorRequest` fires with
    - errorType: ERROR_HTTPS_ONLY
    - uri: https://expired.badssl.com/
- the error page for https-only mode is shown

* If the full url - `https://expired.badssl.com` is accessed the expected error page will be shown.
Issue reproduceable in Fenix, Focus and on Desktop.

STRs:
- enable https-only mode
- type in the url bar: `expired.badssl.com` (seems like any subdomains would work in reproducing the issue)

Expected result:
- Engine's `RequestInterceptor`'s `onErrorRequest` fires with ERROR_SECURITY_BAD_CERT
- the error page for "secure connection failed" is shown

Actual result:
- Engine's `RequestInterceptor`'s `onErrorRequest` fires with
    - errorType: ERROR_HTTPS_ONLY
    - uri: https://expired.badssl.com/
- the error page for https-only mode is shown

 
** If the full url - `https://expired.badssl.com` is accessed the expected error page will be shown.
Issue reproduceable in Fenix, Focus and on Desktop.

STRs:
- enable https-only mode
- type in the url bar: `expired.badssl.com` (seems like any subdomains would work in reproducing the issue)

Expected result:
- Engine's `RequestInterceptor`'s `onErrorRequest` fires with ERROR_SECURITY_BAD_CERT
- the error page for "secure connection failed" is shown

Actual result:
- Engine's `RequestInterceptor`'s `onErrorRequest` fires with
    - errorType: ERROR_HTTPS_ONLY
    - uri: https://expired.badssl.com/
- the error page for https-only mode is shown

 
** If the full url - `https://expired.badssl.com` is accessed the expected scenario happens.

Back to Bug 1759114 Comment 0