Basic authentication is broken (straight to 401)

ungoogled-software / ungoogled-chromium-android

Android build for ungoogled-chromium

GNU General Public License v3.0

491 stars 43 forks source link

Basic authentication is broken (straight to 401) #104

Closed ltguillaume closed 2 years ago

ltguillaume commented 2 years ago

Please at least answer all questions marked with * below. Issues without answering these questions will be closed.

*Device info (please complete the following information):

Device: Samsung Galaxy S5
OS: LineageOS 17.1
Arch: arm
Version: 94.0.4606.71

*Is the bug related to extensions? No

*If not related to extensions, can the bug be reproduced with corresponding Chromium version? No

*Describe the bug When accessing a website that uses HTTP basic authentication, the browser won't ask for a username and password. Instead, it will directly show the 401 error page. Adding the username inside the URI (https://user:pass@location) won't work either.

*To Reproduce Steps to reproduce the behavior:

Go to any page using basic authentication
See 401 warning

*Expected behavior The browser should show a popup window to fill in credentials, or use the user/pass combination embedded in the URI.

Bromite, for example, does not exhibit this behavior.

wchen342 commented 2 years ago

I tested 94.0.4606.81 on http://httpbin.org/basic-auth/foo/bar and it works fine. Can you try the new version? Also maybe cache is playing a role, can you try with a new installation? Also do you have flags enabled?

ltguillaume commented 2 years ago

v94.0.4606.71 is the latest via the F-Droid repo, but I've installed .81 now. For http://httpbin.org/basic-auth/foo/bar I get "This page isn't working HTTP ERROR 401" (slightly different from a my own, but both with 401.
I have no cache of this site, so that's not a factor. Still, I cleared everything, but to no avail.
Then I wiped all app data and tried again: this worked. I reset everything to my preference, one setting at a time, but it didn't make a difference: everything's working now. I guess something in the profile got corrupted (due to an update)? Thanks for the help!

By the way, the F-Droid repos are sometimes pretty far behind: the WebView is still on v92.0.4515.159

wchen342 commented 2 years ago

By the way, the F-Droid repos are sometimes pretty far behind: the WebView is still on v92.0.4515.159

The old Webview version is due to some problems with v93 so I only updated the chromium part. Normally F-Droid will be several days later than Github releases because I need to manually update it.

ltguillaume commented 2 years ago

Ah ok. I just updated manually to https://github.com/ungoogled-software/ungoogled-chromium-android/releases/tag/94.0.4606.81-1-webview (no problems so far), but I understand the reason behind it then.

wchen342 commented 2 years ago

No problem, I will consider this solved now and close this.