New issue
Advanced search Search tips

Issue 871035 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner: ----
Closed: Aug 6
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 2
Type: Bug



Sign in to add a comment

Can't Login to Sites with --single-process

Reported by johny...@gmail.com, Aug 4

Issue description

UserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/67.0.3396.87 Safari/537.36 OPR/54.0.2952.65

Steps to reproduce the problem:
Chrome Version       : Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/67.0.3396.87 Safari/537.36 OPR/54.0.2952.65

URLs (if applicable) : https://forums.opera.com, https://forum.xfce.org/

Other browsers tested: 
    - same browser WITHOUT `--single-process`: OK

What steps will reproduce the problem?
(1) go to login url (above)
(2) enter username/password

What is the expected behavior?
- logged in

What went wrong?
i receive "403 Request Forbidden"

Did this work before? Yes same version, WITHOUT --single-process

Chrome version: 67.0.3396.87  Channel: stable
OS Version: 4.15.0-29-generic #31-Ubuntu SMP Tue Jul 17 15:39:52 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
Flash Version: disabled
 
I run as single process to reduce RAM footprint, and would like to keep it that way.
Components: Internals>Sandbox>SiteIsolation Internals>Network>Proxy
Labels: -Type-Bug-Security -Restrict-View-SecurityTeam Restrict-View-Google Type-Bug
Thanks for the report. This is not a security issue. Removing from the security queue.
Components: Internals>Network>Auth
Labels: -Restrict-View-Google
Not sure if we care about this enough to fix it - the flag is mostly intended for debugging Chrome, I believe.
Issue 474698 could be related -- are you using a PAC script?

Navigate to chrome://net-internals/#proxy to confirm.
Comment 4: Agreed.  Using --single-process puts up a banner saying "You are using an unsupported command-line flag: --single-process. Stability and security will suffer."  I don't think we tend to put in effort maintaining this mode outside of tests, since it's not a safe way to browse the web at all-- there's no sandbox, among other things.

That said, I'm curious about the Site Isolation component added here.  Does the problem go away if you run with --disable-site-isolation-trials?
update: i am testing with fresh Opera install, and no longer getting this issue. 

I suspect one of two possible causes:

- some flag that i had changed in about:flags
- may have been running Opera as snap installation, which caused some unrelated issues. Now running in non-snap PPA installation. 
Status: WontFix (was: Unconfirmed)
Closing the issue (Per comment 7)

Sign in to add a comment