-
Notifications
You must be signed in to change notification settings - Fork 168
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Public links asking for user and password (basic auth popup) #5727
Comments
I've come across this when developing, IIRC it was either an unauthenticated webdav request or a version clash between the |
cc @ChrisEdS |
Possibly a (partial) duplicate #6157 |
Also #6033 |
Can you still reproduce? |
I can reproduce this with oC 10 only. oCIS
oC 10
|
Fix #5727: Do not show auth popup for password protected links in oC 10
Steps to reproduce
Expected behaviour
A password field to open the public shared file or folder should appear.
Actual behaviour
The site loads almost as expected, except that the browser asks for username and password. When pressing Cancel or the ESC key the prompt disappear and the regular public share password needs to be entered.
Server configuration
Operating system: Ubuntu 18.04.5 LTS
Web server: apache 2.4.48
Database: mysql 5.7.35-0ubuntu0.18.04.1
PHP version: 7.4.21
ownCloud version: 10.8
Updated from an older ownCloud or fresh install: update from 10.7
Where did you install ownCloud from: oC tar
Signing status (ownCloud 9.0 and above): signed
The content of config/config.php:
List of activated apps:
Are you using external storage, if yes which one: no
Are you using encryption: no
Are you using an external user-backend, if yes which one: no
Client configuration
Browser: Chrome/Firefox
Operating system: Windows 10
Logs
Web server access log
Web server error log
ownCloud log (data/owncloud.log)
Ticket origin
https://central.owncloud.org/t/public-links-asking-for-user-and-password/33666
As soon as resolved, post solution in central. Same for further questions regarding this ticket.
The text was updated successfully, but these errors were encountered: