You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Being able to accept a self-signed certificate in either Chrome or Firefox.
Actual Behavior
It's actually working for me in Chrome at the moment, but for other reasons (this) I have to use Firefox to test certain network-dependent features of my app.
At other times, this has not worked in Chrome, and yet other times it actually did work in Firefox, though I couldn't tell you what I changed to make it so, sorry.
At the moment, my issue in Firefox is similar to [this older issue]#2313) - at one time, I was able to just accept the self-signed certificate in Firefox, but now the button that used to allow me to do that has vanished, it isn't there anymore.
It's like there are two different UIs for this problem, both in Chrome and Firefox, and for some reason, under certain circumstances, you're either allowed to accept the self-signed certificate, or you're not. When you're not presented with the button, there's no way to load the page.
I'm using a local host name dev.gatewayapi.com, as you can tell from the config I posted, and I'm wondering if perhaps they've tightened the rules in Firefox more recently, that maybe this has to match the request host-name in the browser? Which it wouldn't, since it's hard coded as localhost, and also isn't listed in altNames.
I don't understand precisely how this stuff works, but that's the only clue I could come up with.
Any ideas?
For Bugs; How can we reproduce the behavior?
I wish I could tell you, but this one seems to come and go. 😐
The text was updated successfully, but these errors were encountered:
I am not sure if this issue is related to my issue, but I am getting weird issues in Firefox. I use Stimulus (JavaScript framework) in my application but any modification I do in one of Stimulus controller, it does not get reflected(loaded), but it works fine on Chrome.
Code
Expected Behavior
Being able to accept a self-signed certificate in either Chrome or Firefox.
Actual Behavior
It's actually working for me in Chrome at the moment, but for other reasons (this) I have to use Firefox to test certain network-dependent features of my app.
At other times, this has not worked in Chrome, and yet other times it actually did work in Firefox, though I couldn't tell you what I changed to make it so, sorry.
At the moment, my issue in Firefox is similar to [this older issue]#2313) - at one time, I was able to just accept the self-signed certificate in Firefox, but now the button that used to allow me to do that has vanished, it isn't there anymore.
It's like there are two different UIs for this problem, both in Chrome and Firefox, and for some reason, under certain circumstances, you're either allowed to accept the self-signed certificate, or you're not. When you're not presented with the button, there's no way to load the page.
I noticed you're creating your own certificate and it appears this is always issued with a
commonName
attribute oflocalhost
.I'm using a local host name
dev.gatewayapi.com
, as you can tell from the config I posted, and I'm wondering if perhaps they've tightened the rules in Firefox more recently, that maybe this has to match the request host-name in the browser? Which it wouldn't, since it's hard coded aslocalhost
, and also isn't listed inaltNames
.I don't understand precisely how this stuff works, but that's the only clue I could come up with.
Any ideas?
For Bugs; How can we reproduce the behavior?
I wish I could tell you, but this one seems to come and go. 😐
The text was updated successfully, but these errors were encountered: