Skip to content
This repository has been archived by the owner on Dec 11, 2019. It is now read-only.

Going direct to https://wrong.host.badssl.com/ doesn't show certificate #7042

Closed
bbondy opened this issue Feb 3, 2017 · 8 comments
Closed
Labels
bug fixed-with-brave-core This issue will automatically resolved with the replacement of Muon with Brave Core. wontfix

Comments

@bbondy
Copy link
Member

bbondy commented Feb 3, 2017

  • Did you search for similar issues before submitting this one?
    Yes

  • Describe the issue you encountered:
    While testing some certificate fingerprints cause decoding error #6524 I noticed that if you navigate directly to https://wrong.host.badssl.com/ then you can't view the certificate.

  • Platform (Win7, 8, 10? macOS? Linux distro?):
    macOS.

  • Brave Version (revision SHA):
    0.13.2-rc3

  • Steps to reproduce:

    1. Go to https://wrong.host.badssl.com/
  • Actual result:
    Notice that there is no view certificate option.

  • Expected result:
    There should be a view certificate option.

  • Will the steps above reproduce in a fresh profile? If not what other info can be added?
    Yes

  • Is this an issue in the currently released version?
    Not sure

  • Can this issue be consistently reproduced?
    No but it happens frequently pretty easily. Do a new tab and load https://wrong.host.badssl.com/, then keep repeating with new tab and loading that URL until you see it.

  • Screenshot if needed:

screenshot 2017-02-03 15 39 33

  • Any related issues:
@bbondy bbondy added this to the 0.13.2 milestone Feb 3, 2017
@bbondy
Copy link
Member Author

bbondy commented Feb 3, 2017

Note that if you first go to badssl.com and then click through, it does work in that case.

@luixxiul
Copy link
Contributor

luixxiul commented Feb 4, 2017

I cannot reproduce the issue on Windows 10 32 bit. Maybe this is specific to macOS.

@cndouglas
Copy link

I cannot reproduce with a fresh profile, Brave 0.13.2 RC 3 (1d936db), macOS 10.12.x.

  1. Open a new tab.
  2. Paste https://wrong.host.badssl.com/ in the URLbar.
  3. Press Enter.

@luixxiul luixxiul added the needs-info Another team member needs information from the PR/issue opener. label Feb 4, 2017
@luixxiul
Copy link
Contributor

luixxiul commented Feb 4, 2017

@bbondy do you experience the issue in the same tab as you tested #6524? Or in a new tab?

I think I noticed the same thing when I was going back and forward the error page on the same tab. But maybe this can be another issue.

@bbondy bbondy removed the needs-info Another team member needs information from the PR/issue opener. label Feb 4, 2017
@bbondy
Copy link
Member Author

bbondy commented Feb 4, 2017

I updated the info in the original post. I thought I could reproduce every time but I didn't realize that it only happens sometimes. If you keep opening a new tab and loading https://wrong.host.badssl.com/ then you should reproduce, for me in about half of the loads.

@luixxiul
Copy link
Contributor

luixxiul commented Feb 4, 2017

Yes I reproduced too

@darkdh
Copy link
Member

darkdh commented Feb 4, 2017

Updated the STR:

scenario 1: (it exists since 0.12.5)

  1. bookmark https://wrong.host.badssl.com/
  2. middle click on the bookmark of step1
  3. see the opened new tab

scenario 2: (introduced in 0.13.0)

  1. middle click https://wrong.host.badssl.com/ from this comment
  2. new opened tab will not load anything until you reload it
  3. the tab after reload still cannot see certificate detail

@bbondy
Copy link
Member Author

bbondy commented Feb 5, 2017

Since it exists since 0.12 series I'm removing from this milestone.

@bbondy bbondy removed this from the 0.13.2 milestone Feb 5, 2017
@luixxiul luixxiul added the bug label Feb 5, 2017
@bsclifton bsclifton added this to the Triage Backlog milestone Nov 27, 2017
@bsclifton bsclifton added wontfix fixed-with-brave-core This issue will automatically resolved with the replacement of Muon with Brave Core. labels Aug 30, 2018
@bsclifton bsclifton removed this from the Triage Backlog milestone Aug 30, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug fixed-with-brave-core This issue will automatically resolved with the replacement of Muon with Brave Core. wontfix
Projects
None yet
Development

No branches or pull requests

5 participants