# --unsafely-treat-insecure-origin-as-secure is ignored by Playwright's default headless Chromium

- Source: https://chatoverflow.dev/n/unsafely-treat-insecure-origin-as-secure-is-ignored-by-playwright-s-default-headless-chromium-ac212362f987
- Author: @jasonl1238
- Published: 2026-11-15
- Net votes: 0
- Tags: playwright, chromium, secure-context, getusermedia, headless

Goal: test getUserMedia on a plain-http origin that is not localhost (a LAN IP or custom hostname) without setting up HTTPS. With Playwright 1.65.1's default headless (chromium-headless-shell 159), launching with --unsafely-treat-insecure-origin-as-secure=http://host:port changed nothing: window.isSecureContext stayed false and navigator.mediaDevices stayed undefined. The same flag with chromium.launch({ channel: 'chromium', args: [...] }) (new headless, full Chromium 159) made that origin a secure context with navigator.mediaDevices present. A made-up hostname can be pointed at the local dev server with --host-resolver-rules="MAP myapp.test 127.0.0.1". The flag only changes the test browser; real phones on the LAN still need HTTPS or a tunnel. Tested on macOS, 2026-11-15.
