| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
accessible component and a DAV accessible component so that we can eliminate the http-auth prompts for web-accessed resources.
|
|
|
| |
I could not find out under which conditions this is relevant and therefore have no test case, but it must be of instance RedDAV\RedFile.
|
|
|
|
|
|
| |
Finished moving classes out from include/reddav.php into own files. Also
continued with namespace for RedDAV.
Improved some docs and added some todos and fixmes.
|
| |
|
|
|
|
|
|
|
|
|
| |
First step on cleaning up ReadDAV classes and restructuring it bit in
preparation for adding some more DAV features, photo access, CalDAV, etc.
and hopefully also some PHPunits.
Add a PHP5.3 namespace for RedDAV classes. Any objections against this or
the vendor namespace?
Add some more documentation for RedBrowser.
|
|
|
|
|
| |
Removed some duplicate code in RedBasicAuth and restructured a bit.
Still work in progress.
|
| |
|
| |
|
|
|
|
|
| |
If a folder was empty a zero timestamp was returned. Now it will
return the timestamp of the folder itself.
|
| |
|
|
|
|
| |
when somebody tries to view the link
|
|
|
|
| |
to an un-auth'd person (without asking for a password) by adding a query parameter 'davguest=1'. This is a bit of a hack, but there was no response on the official forum about how to do this correctly so it will have to do. On the downside, if permission is denied, it won't ask for a password - but we're talking about unauthenticated folks who didn't go through magic auth so chances are even if they authenticate, permission will still be denied.
|
| |
|
|
|
|
| |
password is now +++
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
lot of permissions stuff is in place so it's marginally (but probably not completely) permission controlled
|
| |
|
|
|
|
| |
basic framework isn't even close to working. This does break the working test we did have (which was never connected to the Red backend). Now we're starting to connect Red and DAV together intimately. There will probably be some twists and turns along the way as we get the information we need into all the class objects that need them. But the important part is that the RedDirectory and RedFile classes are loading without throwing white screens and from here we can use logging to figure out what the DAV front end is trying to do and what it is passing to the backend and hopefully figure out what it expects to do with the results. Unless you're a competent developer with a strong background in OOP and are helping develop this code, you should keep it an arm's length away from any production site and don't even think of enabling it. By default it is turned off.
|
| |
|
|
mod/cloud.php - there is no other documentation. Use at your own risk. Send all bug reports to nobody@nowhere.com.
|