| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The current logic for mod_rewrite relies on the fact that people have properly configured ownCloud, basically it reads from the `overwrite.cli.ur
l` entry and then derives the `RewriteBase` from it.
This usually works. However, since the ownCloud packages seem to install themselves at `/owncloud` (because subfolders are cool or so…) _a lot_ of people have just created a new Virtual Host for it or have simply symlinked the path etc.
This means that `overwrite.cli.url` is wrong, which fails hard if it is used as RewriteBase since Apache does not know where it should serve files from. In the end the ownCloud instance will not be accessible anymore and users will be frustrated. Also some shared hosters like 1&1 (because using shared hosters is so awesome… ;-)) have somewhat dubious Apache configurations or use versions of mod_rewrite from the mediveal age. (because updating is money or so…)
Anyhow. This makes this explicitly an opt-in configuration flag. If `htaccess.RewriteBase` is set then it will configure index.php-less URLs, if
admins set that after installation and don't want to wait until the next ownCloud version they can run `occ maintenance:update:htaccess`.
For ownCloud 9.0 we also have to add a repair step to make sure that instances that already have a RewriteBase configured continue to use it by copying it into the config file. That way all existing URLs stay valid. That one is not in this PR since this is unneccessary in master.
Effectively this reduces another risk of breakage when updating from ownCloud 8 to ownCloud 9.
Fixes https://github.com/owncloud/core/issues/24525, https://github.com/owncloud/core/issues/24426 and probably some more.
|
|
|
|
|
|
| |
* Move Application to correct namespace and PSR-4 it
* Move dav app to PSR-4
|
|
|
|
|
|
|
|
| |
* Move Encryption to PSR-4
* Move encryption tests to PSR-4
* Fix the tests
|
| |
|
|
|
|
| |
Opening a permalink that points to a trashed file will now display the
file within the "Deleted Files" section in the files web UI.
|
| |
|
|
|
| |
Fixes the redirection after login, otherwise `core/files/index` is opened which fails.
|
|
|
|
|
|
|
|
| |
* Move app to PSR-4
* Fix setUp method
* Fix the tests
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* allow configuration of memcache options
Use production values for memcached as explained in http://apprize.info/php/scaling/15.html
The current implementiation uses ascii based serialization. This PR should reduce traffic to the memcached server.
cc @MorrisJobke @FelixBoehm
* add config sample
* merge config options, throw hint on config error
* fix typo
* fix config sample
|
|\
| |
| | |
Fix etag propegation test race condition
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
E-tag propagation replies on the mtime of the file. Order of events:
1. add file 'foo.txt' with content 'bar'
2. Set mtime to now() - 1
3. Check if etag changed.
Now this goes right often when 1 and 2 happen in the same second.
However imagine
1. add file 'foo.txt' with content 'bar' (at t=0.999)
2. Set mtime to now() - 1 (at t=1.001)
Now the mtime will be set to the same time. Thus not chaning the etag.
|
|\ \
| | |
| | | |
Correctly register PSR-4 autoloading before install.php and loading commands
|
| |/ |
|
|\ \
| |/
|/| |
Pluggable auth
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| | |
add some range to time() assertions
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| | |
add token type column and delete only temporary tokens in the background job
debounce token updates; fix wrong class import
|
| | |
|
| |
| |
| |
| |
| | |
* Update last_activity timestamp of the session token
* Check user backend credentials once in 5 minutes
|
| |
| |
| |
| | |
add 'last_activity' column to session tokens and delete old ones via a background job
|
|/
|
|
|
|
|
|
| |
* Add InvalidTokenException
* add DefaultTokenMapper and use it to check if a auth token exists
* create new token for the browser session if none exists
hash stored token; save user agent
* encrypt login password when creating the token
|
|\
| |
| | |
Move \OCP\Command to PSR-4
|
| | |
|
|\ \
| | |
| | | |
lib/private/user to PSR-4
|
| | | |
|
| | |
| | |
| | |
| | |
| | | |
Since some apps (ldap et al) still depend on OC_User_Backend this seemed
like the cleanest approach.
|
| | | |
|
| | | |
|
| |/ |
|
|\ \
| | |
| | | |
Yo-ho-oh - Murder all band 'o pirates
|
|/ / |
|