5 ms·
For local development, Chrome has a flag that lets you force specific origins to be treated as secure: chrome://flags/#unsafely-treat-insecure-origin-as-secu
by varenc 7y ago
For local development, Chrome has a flag that lets you force specific origins to be treated as secure:
chrome://flags/#unsafely-treat-insecure-origin-as-secure
I don't think Firefox has anything equivalent though? This bug on the topic is unassigned: https://bugzilla.mozilla.org/show_bug.cgi?id=1410365 https://bugzilla.mozilla.org/show_bug.cgi?id=1410365
- mort96 7y agoI don't imagine that works on mobile chrome, which is what the parent comment was talking about.
- _fzslm 7y agoIt does, on Android.
- mort96 7y agoAh, TIL. Though it doesn't work on iOS Chrome, and you want to test on iOS too obviously.
- deleted 7y ago[deleted]
- Wowfunhappy 7y agoiOS Chrome is just Safari with a Google skin, Google has no control over this type of thing.
- mort96 7y agoThat's both true and completely irrelevant.
- Wowfunhappy 7y agoWell, it's relevant insofar as you're complaining to the wrong company. Does this behavior even exists in iOS Chrome? If it does, it exists in Mobile Safari as well.
- mort96 7y agoI... wasn't complaining about Google though? I said you can't enable chrome://flags/#unsafely-treat-insecure-origin-as-secure (or an equivalent) on iOS, not that it's Google's fault that you can't.
- deleted 7y ago[deleted]
- aaronharnly 7y agoInteresting! Though I find that behaves rather strangely – seems to clear itself on every launch.
- varenc 7y agoYea that's annoying, but I believe that's intentional... you can pass that flag in as an arg when you launch chrome though so you don't have to set it up each time.