mirror of
https://github.com/nextcloud/documentation.git
synced 2026-01-03 02:09:45 +07:00
Merge pull request #2013 from RealRancor/well_known_doc
Updating .well-known documentation and new dav endpoint for 9.0 release
This commit is contained in:
Carla Schroder
@@ -66,7 +66,7 @@ you're finished click **Save**.
|
||||
|
||||
The next screen that opens is **Create Client ID**. Check **Web Application**,
|
||||
then enter your app name. **Authorized JavaScript Origins** is your root domain,
|
||||
for example ``https://www.example.com``, without a trailing slash. You need two
|
||||
for example ``https://example.com``, without a trailing slash. You need two
|
||||
**Authorized Redirect URIs**, and they must be in this form::
|
||||
|
||||
https://example.com/owncloud/index.php/settings/personal
|
||||
|
||||
@@ -8,8 +8,8 @@ learn how to configure an ownCloud external storage.
|
||||
|
||||
When filling in the **URL** field, use the path to the root of the ownCloud
|
||||
installation, rather than the path to the WebDAV endpoint. So, for a server at
|
||||
``http://example.com/owncloud``, use ``http://example.com/owncloud`` and not
|
||||
``http://example.com/owncloud/remote.php/webdav``.
|
||||
``https://example.com/owncloud``, use ``https://example.com/owncloud`` and not
|
||||
``https://example.com/owncloud/remote.php/dav``.
|
||||
|
||||
See :doc:`../external_storage_configuration_gui` for additional mount
|
||||
options and information.
|
||||
|
||||
@@ -49,7 +49,7 @@ On Windows hosts running MySQL on the same system changing the parameter
|
||||
from ``localhost`` to ``127.0.0.1`` could improve the page loading time.
|
||||
|
||||
See also `this forum thread
|
||||
<http://forum.owncloud.org/viewtopic.php?f=17&t=7559>`_.
|
||||
<https://forum.owncloud.org/viewtopic.php?f=17&t=7559>`_.
|
||||
|
||||
Other performance improvements
|
||||
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
|
||||
|
||||
@@ -109,4 +109,11 @@ combination with remote hosts using SNI. A technology used by most of the HTTPS
|
||||
websites. To ensure that ownCloud will work properly you need to update OpenSSL
|
||||
to at least 1.0.2b or 1.0.1d. For NSS the patch version depends on your distribution
|
||||
and an heuristic is running the test which actually reproduces the bug. There
|
||||
are distributions such as RHEL/CentOS which have this backport still `pending <https://bugzilla.redhat.com/show_bug.cgi?id=1241172>`_.
|
||||
are distributions such as RHEL/CentOS which have this backport still `pending
|
||||
<https://bugzilla.redhat.com/show_bug.cgi?id=1241172>`_.
|
||||
|
||||
Your web server is not set up properly to resolve /.well-known/caldav/ or /.well-known/carddav/
|
||||
-----------------------------------------------------------------------------------------------
|
||||
|
||||
Both URLs needs to be correctly redirected to the DAV endpoint of ownCloud. Please
|
||||
refer to :ref:`service-discovery-label` for more info.
|
||||
@@ -65,8 +65,8 @@ Nginx Configuration
|
||||
error_page 403 /core/templates/403.php;
|
||||
error_page 404 /core/templates/404.php;
|
||||
|
||||
rewrite ^/.well-known/carddav /remote.php/carddav/ permanent;
|
||||
rewrite ^/.well-known/caldav /remote.php/caldav/ permanent;
|
||||
rewrite ^/.well-known/carddav /remote.php/dav/ permanent;
|
||||
rewrite ^/.well-known/caldav /remote.php/dav/ permanent;
|
||||
|
||||
# The following 2 rules are only needed for the user_webfinger app.
|
||||
# Uncomment it if you're planning to use this app.
|
||||
|
||||
@@ -34,14 +34,14 @@ If you think you have found a bug in ownCloud, please:
|
||||
|
||||
If you can't find a solution, please use our `bugtracker`_.
|
||||
|
||||
.. _the ownCloud Forums: http://forum.owncloud.org
|
||||
.. _the ownCloud Forums: https://forum.owncloud.org
|
||||
.. _FAQ page: https://forum.owncloud.org/viewforum.php?f=17
|
||||
.. _the ownCloud User mailing list:
|
||||
https://mailman.owncloud.org/mailman/listinfo/user
|
||||
.. _webchat: http://webchat.freenode.net/?channels=owncloud
|
||||
.. _Enterprise Subscription: https://owncloud.com/lp/community-or-enterprise/
|
||||
.. _bugtracker:
|
||||
http://doc.owncloud.org/server/9.0/developer_manual/bugtracker/index.html
|
||||
https://doc.owncloud.org/server/9.0/developer_manual/bugtracker/index.html
|
||||
.. TODO ON RELEASE: Update version number above on release
|
||||
|
||||
General Troubleshooting
|
||||
@@ -126,7 +126,7 @@ Disregarding this can lead to unwanted behaviours like:
|
||||
If you need to directly upload files from the same server please use a WebDAV
|
||||
command line client like ``cadaver`` to upload files to the WebDAV interface at:
|
||||
|
||||
https://example.org/owncloud/remote.php/webdav
|
||||
https://example.com/owncloud/remote.php/dav
|
||||
|
||||
Common problems / error messages
|
||||
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
|
||||
@@ -257,36 +257,49 @@ Troubleshooting Contacts & Calendar
|
||||
Service discovery
|
||||
^^^^^^^^^^^^^^^^^
|
||||
|
||||
Some clients - especially iOS - have problems finding the proper sync URL, even
|
||||
when explicitly configured to use it.
|
||||
Some clients - especially on iOS/Mac OS X - have problems finding the proper
|
||||
sync URL, even when explicitly configured to use it.
|
||||
|
||||
There are several techniques to remedy this, which are described extensively at
|
||||
If you want to use CalDAV or CardDAV clients together with ownCloud it is
|
||||
important to have a correct working setup of the following URLs:
|
||||
|
||||
https://example.com/.well-known/carddav
|
||||
https://example.com/.well-known/caldav
|
||||
|
||||
Those need to be redirecting your clients to the correct DAV endpoints. If
|
||||
running ownCloud at the document root of your webserver the correct URL is:
|
||||
|
||||
https://example.com/remote.php/dav
|
||||
|
||||
and if running in a subfolder like ``owncloud``:
|
||||
|
||||
https://example.com/owncloud/remote.php/dav
|
||||
|
||||
For the first case the :file:`.htaccess` file shipped with ownCloud should do
|
||||
this work for your when running Apache. You only need to make sure that your
|
||||
web server is using this file. When running nginx please refer to the
|
||||
:ref:`nginx_configuration_example` example.
|
||||
|
||||
.. note: The following step is important for users using the linux packages
|
||||
/ repositories provided by ownCloud.
|
||||
|
||||
If your ownCloud instance is installed in a subfolder called ``owncloud`` and
|
||||
you're running Apache create or edit the :file:`.htaccess`` file within the
|
||||
document root of your webserver and add the following lines::
|
||||
|
||||
Redirect 301 /.well-known/carddav /owncloud/remote.php/dav
|
||||
Redirect 301 /.well-known/caldav /owncloud/remote.php/dav
|
||||
|
||||
Now change the URL in the client settings to just use ``https://example.com``
|
||||
instead of e.g. ``https://example.com/owncloud/remote.php/dav/principals/username``.
|
||||
|
||||
There are also several techniques to remedy this, which are described extensively at
|
||||
the `Sabre DAV website <http://sabre.io/dav/service-discovery/>`_.
|
||||
|
||||
If your ownCloud instance is installed in a subfolder under the web server's
|
||||
document root and the client has difficulties finding the Cal- or CardDAV
|
||||
end-points, configure your web server to redirect from a "well-known" URL to
|
||||
the
|
||||
one used by ownCloud. When using the Apache web server this is easily achieved
|
||||
using a :file:`.htaccess` file in the document root of your site.
|
||||
|
||||
Say your instance is located in the ``owncloud`` folder, so the URL to it is
|
||||
``ADDRESS/owncloud``, create or edit the :file:`.htaccess` file and add the
|
||||
following lines::
|
||||
|
||||
Redirect 301 /.well-known/carddav /owncloud/remote.php/carddav
|
||||
Redirect 301 /.well-known/caldav /owncloud/remote.php/caldav
|
||||
|
||||
Now change the URL in the client settings to just use ``ADDRESS`` instead of
|
||||
e.g. ``ADDRESS/remote.php/carddav/principals/username``.
|
||||
|
||||
This problem is being discussed in the `forum
|
||||
<http://forum.owncloud.org/viewtopic.php?f=3&t=71&p=2211#p2197>`_.
|
||||
|
||||
Unable to update Contacts or Events
|
||||
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
|
||||
|
||||
If you get an error like ``PATCH https://ADDRESS/some_url HTTP/1.0 501 Not
|
||||
If you get an error like ``PATCH https://example.com/remote.php/dav HTTP/1.0 501 Not
|
||||
Implemented`` it is likely caused by one of the following reasons:
|
||||
|
||||
Using Pound reverse-proxy/load balancer
|
||||
@@ -295,6 +308,10 @@ Using Pound reverse-proxy/load balancer
|
||||
<http://www.apsis.ch/pound/pound_list/archive/2013/2013-08/1377264673000>`_
|
||||
to support HTTP/1.1.
|
||||
|
||||
Misconfigured web server
|
||||
Your webserver is misconfigured and blocks the needed DAV methods.
|
||||
Please refer to ``Troubleshooting WebDAV`` above for troubleshooting steps.
|
||||
|
||||
Other issues
|
||||
------------
|
||||
|
||||
|
||||
@@ -423,8 +423,8 @@ Tips
|
||||
|
||||
* Credentials must be set before calling any method
|
||||
* Paths must not be on URL Encoding
|
||||
* Correct path: ``http://www.myowncloudserver.com/owncloud/remote.php/webdav/PopMusic``
|
||||
* Wrong path: ``http://www.myowncloudserver.com/owncloud/remote.php/webdav/Pop%20Music/``
|
||||
* Correct path: ``https://example.com/owncloud/remote.php/dav/PopMusic``
|
||||
* Wrong path: ``https://example.com/owncloud/remote.php/dav/Pop%20Music/``
|
||||
* There are some forbidden characters to be used in folder and files names on the server, same on the ownCloud Android Library "\","/","<",">",":",""","|","?","*"
|
||||
* Upload and download actions may be cancelled thanks to the objects uploadOperation.cancel(), downloadOperation.cancel()
|
||||
* Unit tests, before launching unit tests you have to enter your account information (server url, user and password) on TestActivity.java
|
||||
|
||||
@@ -242,7 +242,7 @@ Always validate the URL before redirecting if the requested URL is on the same d
|
||||
.. code-block:: php
|
||||
|
||||
<?php
|
||||
header('Location: http://www.example.com'. $_GET['redirectURL']);
|
||||
header('Location: https://example.com'. $_GET['redirectURL']);
|
||||
|
||||
Getting help
|
||||
------------
|
||||
|
||||
@@ -810,8 +810,8 @@ Tips
|
||||
|
||||
* Credentials must be set before calling any method
|
||||
* Paths must not be on URL Encoding
|
||||
* Correct path: ``http://www.myowncloudserver.com/owncloud/remote.php/webdav/Pop_Music/``
|
||||
* Wrong path: ``http://www.myowncloudserver.com/owncloud/remote.php/webdav/Pop%20Music/``
|
||||
* Correct path: ``https://example.com/owncloud/remote.php/dav/Pop_Music/``
|
||||
* Wrong path: ``https://example.com/owncloud/remote.php/dav/Pop%20Music/``
|
||||
* There are some forbidden characters to be used in folder and files names on the server, same on the ownCloud iOS library "\", "/","<",">",":",""","","?","*"
|
||||
* To move a folder the origin path and the destination path must end with “/”
|
||||
* To move a file the origin path and the destination path must not end with “/”
|
||||
|
||||
@@ -27,14 +27,14 @@ Apple iOS devices is by using the `ownCloud mobile apps
|
||||
To connect to your ownCloud server with the **ownCloud** mobile apps, use the
|
||||
base URL and folder only::
|
||||
|
||||
example.org/owncloud
|
||||
example.com/owncloud
|
||||
|
||||
In addition to the mobile apps provided by ownCloud, you can use other apps to
|
||||
connect to ownCloud from your mobile device using WebDAV. `WebDAV Navigator`_ is
|
||||
a good (proprietary) app for `Android devices`_, `iPhones`_, and `BlackBerry
|
||||
devices`_. The URL to use on these is::
|
||||
|
||||
example.org/owncloud/remote.php/webdav
|
||||
example.com/owncloud/remote.php/dav
|
||||
|
||||
WebDAV Configuration
|
||||
--------------------
|
||||
@@ -46,7 +46,7 @@ Distributed Authoring and Versioning (WebDAV) is a Hypertext Transfer Protocol
|
||||
servers. With WebDAV you can access your ownCloud shares on Linux, Mac OS X and
|
||||
Windows in the same way as any remote network share, and stay synchronized.
|
||||
|
||||
.. note:: In the following examples, You must adjust **example.org/** to the
|
||||
.. note:: In the following examples, You must adjust **example.com/** to the
|
||||
URL of your ownCloud server installation.
|
||||
|
||||
Accessing Files Using Linux
|
||||
@@ -60,7 +60,7 @@ Nautilus File Manager
|
||||
Use the ``davs://`` protocol to connect the Nautilus file manager to your
|
||||
ownCloud share::
|
||||
|
||||
davs://example.org/owncloud/remote.php/webdav
|
||||
davs://example.com/owncloud/remote.php/dav
|
||||
|
||||
.. note:: If your server connection is not HTTPS-secured, use `dav://` instead
|
||||
of `davs://`.
|
||||
@@ -74,7 +74,7 @@ Accessing Files with KDE and Dolphin File Manager
|
||||
To access your ownCloud files using the Dolphin file manager in KDE, use
|
||||
the ``webdav://`` protocol::
|
||||
|
||||
webdav://example.org/owncloud/remote.php/webdav
|
||||
webdav://example.com/owncloud/remote.php/dav
|
||||
|
||||
.. image:: ../images/webdav_dolphin.png
|
||||
:alt: screenshot of configuring Dolphin file manager to use WebDAV
|
||||
@@ -92,9 +92,9 @@ You can create a permanent link to your ownCloud server:
|
||||
|
||||
* User: The ownCloud username you used to log in, for example admin.
|
||||
|
||||
* Server: The ownCloud domain name, for example **example.org** (without
|
||||
* Server: The ownCloud domain name, for example **example.com** (without
|
||||
**http://** before or directories afterwards).
|
||||
* Folder -- Enter the path ``owncloud/remote.php/webdav``.
|
||||
* Folder -- Enter the path ``owncloud/remote.php/dav``.
|
||||
#. (Optional) Check the "Create icon checkbox" for a bookmark to appear in the
|
||||
Places column.
|
||||
#. (Optional) Provide any special settings or an SSL certificate in the "Port &
|
||||
@@ -140,11 +140,11 @@ automatically every time you log in to your Linux computer.
|
||||
6. Add your ownCloud login credentials to the end of the ``secrets`` file,
|
||||
using your ownCloud server URL and your ownCloud username and password::
|
||||
|
||||
example.org/owncloud/remote.php/webdav <username> <password>
|
||||
example.com/owncloud/remote.php/dav <username> <password>
|
||||
|
||||
7. Add the mount information to ``/etc/fstab``::
|
||||
|
||||
example.org/owncloud/remote.php/webdav /home/<username>/owncloud
|
||||
example.com/owncloud/remote.php/dav /home/<username>/owncloud
|
||||
davfs user,rw,auto 0 0
|
||||
|
||||
8. Then test that it mounts and authenticates by running the following
|
||||
@@ -210,7 +210,7 @@ To access files through the Mac OS X Finder:
|
||||
For example, the URL used to connect to the ownCloud server
|
||||
from the Mac OS X Finder is::
|
||||
|
||||
http://example.org/owncloud/remote.php/webdav
|
||||
https://example.com/owncloud/remote.php/dav
|
||||
|
||||
.. image:: ../images/osx_webdav2.png
|
||||
|
||||
@@ -254,12 +254,12 @@ the drive:
|
||||
2. Enter the following line in the command prompt to map to the computer Z
|
||||
drive::
|
||||
|
||||
net use Z: https://<drive_path>/remote.php/webdav /user:youruser
|
||||
net use Z: https://<drive_path>/remote.php/dav /user:youruser
|
||||
yourpassword
|
||||
|
||||
where <drive_path> is the URL to your ownCloud server.
|
||||
|
||||
For example: ``net use Z: https://example.org/owncloud/remote.php/webdav
|
||||
For example: ``net use Z: https://example.com/owncloud/remote.php/dav
|
||||
/user:youruser yourpassword``
|
||||
|
||||
The computer maps the files of your ownCloud account to the drive letter Z.
|
||||
@@ -271,7 +271,7 @@ For example: ``net use Z: https://example.org/owncloud/remote.php/webdav
|
||||
|
||||
An alternative command syntax is::
|
||||
|
||||
net use Z: \\example.org@ssl\owncloud\remote.php\webdav /user:youruser
|
||||
net use Z: \\example.com@ssl\owncloud\remote.php\dav /user:youruser
|
||||
yourpassword
|
||||
|
||||
Mapping Drives With Windows Explorer
|
||||
@@ -284,11 +284,11 @@ To map a drive using the Microsoft Windows Explorer:
|
||||
the drop-down menu.
|
||||
3. Choose a local network drive to which you want to map ownCloud.
|
||||
4. Specify the address to your ownCloud instance, followed by
|
||||
**/remote.php/webdav**.
|
||||
**/remote.php/dav**.
|
||||
|
||||
For example::
|
||||
|
||||
https://example.org/owncloud/remote.php/webdav
|
||||
https://example.com/owncloud/remote.php/dav
|
||||
|
||||
.. note:: For SSL protected servers, check **Reconnect at logon** to ensure
|
||||
that the mapping is persistent upon subsequent reboots. If you want to
|
||||
@@ -317,7 +317,7 @@ To use Cyberduck:
|
||||
|
||||
1. Specify a server without any leading protocol information. For example:
|
||||
|
||||
``example.org``
|
||||
``example.com``
|
||||
|
||||
2. Specify the appropriate port. The port you choose depends on whether or not
|
||||
your ownCloud server supports SSL. Cyberduck requires that you select a
|
||||
@@ -330,7 +330,7 @@ different connection type if you plan to use SSL. For example:
|
||||
3. Use the 'More Options' drop-down menu to add the rest of your WebDAV URL into
|
||||
the 'Path' field. For example:
|
||||
|
||||
``remote.php/webdav``
|
||||
``remote.php/dav``
|
||||
|
||||
Now Cyberduck enables file access to the ownCloud server.
|
||||
|
||||
@@ -437,29 +437,29 @@ To create a folder with the current date as name:
|
||||
|
||||
.. code-block:: bash
|
||||
|
||||
$ curl -u user:pass -X MKCOL "http://example.org/owncloud/remote.php/webdav/$(date '+%d-%b-%Y')"
|
||||
$ curl -u user:pass -X MKCOL "https://example.com/owncloud/remote.php/dav/$(date '+%d-%b-%Y')"
|
||||
|
||||
To upload a file ``error.log`` into that directory:
|
||||
|
||||
.. code-block:: bash
|
||||
|
||||
$ curl -u user:pass -T error.log "http://example.org/owncloud/remote.php/webdav/$(date '+%d-%b-%Y')/error.log"
|
||||
$ curl -u user:pass -T error.log "https://example.com/owncloud/remote.php/dav/$(date '+%d-%b-%Y')/error.log"
|
||||
|
||||
To move a file:
|
||||
|
||||
.. code-block:: bash
|
||||
|
||||
$ curl -u user:pass -X MOVE --header 'Destination: http://example.org/owncloud/remote.php/webdav/target.jpg' http://example.org/owncloud/remote.php/webdav/source.jpg
|
||||
$ curl -u user:pass -X MOVE --header 'Destination: https://example.com/owncloud/remote.php/dav/target.jpg' https://example.com/owncloud/remote.php/dav/source.jpg
|
||||
|
||||
To get the properties of files in the root folder:
|
||||
|
||||
.. code-block:: bash
|
||||
|
||||
$ curl -X PROPFIND -H "Depth: 1" -u user:pass http://example.org/owncloud/remote.php/webdav/ | xml_pp
|
||||
$ curl -X PROPFIND -H "Depth: 1" -u user:pass https://example.com/owncloud/remote.php/dav/ | xml_pp
|
||||
<?xml version="1.0" encoding="utf-8"?>
|
||||
<d:multistatus xmlns:d="DAV:" xmlns:oc="http://owncloud.org/ns" xmlns:s="http://sabredav.org/ns">
|
||||
<d:response>
|
||||
<d:href>/owncloud/remote.php/webdav/</d:href>
|
||||
<d:href>/owncloud/remote.php/dav/</d:href>
|
||||
<d:propstat>
|
||||
<d:prop>
|
||||
<d:getlastmodified>Tue, 13 Oct 2015 17:07:45 GMT</d:getlastmodified>
|
||||
@@ -474,7 +474,7 @@ To get the properties of files in the root folder:
|
||||
</d:propstat>
|
||||
</d:response>
|
||||
<d:response>
|
||||
<d:href>/owncloud/remote.php/webdav/welcome.txt</d:href>
|
||||
<d:href>/owncloud/remote.php/dav/welcome.txt</d:href>
|
||||
<d:propstat>
|
||||
<d:prop>
|
||||
<d:getlastmodified>Tue, 13 Oct 2015 17:07:35 GMT</d:getlastmodified>
|
||||
|
||||
@@ -36,7 +36,9 @@ The Calendar app contains the following fields and controls:
|
||||
controls include sharing, obtaining an external URL link to the calendar, an
|
||||
export function, an edit function, and a delete (trash) button.
|
||||
|
||||
.. note:: Some Ad-Block plugins hide the "Share" button for calendars. If the "Share" button is missing, try disabling your Ad-Block plugin or add a whitelist-entry for your OwnCloud instance.
|
||||
.. note:: Some Ad-Block plugins hide the "Share" button for calendars. If the
|
||||
"Share" button is missing, try disabling your Ad-Block plugin or add a
|
||||
whitelist-entry for your OwnCloud instance.
|
||||
|
||||
- Calendar Settings -- Provides access to the calendar-specific settings. These
|
||||
settings include the calendar timezone selection, time format selection, week
|
||||
@@ -299,11 +301,11 @@ Additionally the Calendar app is providing two URLs for special functions:
|
||||
|
||||
**Export calendar as an .ics file**
|
||||
|
||||
https://ADDRESS/remote.php/caldav/calendars/USERNAME/CALENDARNAME?export
|
||||
https://example.com/remote.php/dav/calendars/USERNAME/CALENDARNAME?export
|
||||
|
||||
**Your contacts' birthdays**
|
||||
|
||||
https://ADDRESS/remote.php/caldav/calendars/USERNAME/contact_birthdays
|
||||
https://example.com/remote.php/dav/calendars/USERNAME/contact_birthdays
|
||||
|
||||
Calendar App FAQ
|
||||
----------------
|
||||
|
||||
@@ -272,10 +272,12 @@ Synchronizing With Android
|
||||
|
||||
To synchronize with an Android device:
|
||||
|
||||
1) Install CardDAV- Sync free from the Google play store by visiting `this link <https://play.google.com/store/apps/details?id=org.dmfs.carddav.sync>`_.
|
||||
1) Install CardDAV- Sync free from the Google play store by visiting `this link
|
||||
<https://play.google.com/store/apps/details?id=org.dmfs.carddav.sync>`_.
|
||||
This app supports auto-configuration.
|
||||
|
||||
.. note:: Following the installing, visit carddavs://example.org/remote.php/carddav/ to auto-configure the app.
|
||||
.. note:: Following the installation, visit carddavs://example.com/remote.php/dav/
|
||||
to auto-configure the app.
|
||||
|
||||
3) Enter your login details.
|
||||
|
||||
@@ -298,7 +300,7 @@ To synchronize with an Apple iOS device:
|
||||
|
||||
5. Select ``Add CardDAV account``.
|
||||
|
||||
6. For ``server``, enter http://example.org/remote.php/carddav/principals/username
|
||||
6. For ``server``, enter https://example.com/remote.php/dav/principals/username
|
||||
|
||||
7. Specify your username and password.
|
||||
|
||||
@@ -339,7 +341,7 @@ Additionally, the Contacts app is providing an URL for special functions:
|
||||
|
||||
**Export an address book as a vCard file**
|
||||
|
||||
https://ADDRESS/remote.php/carddav/addressbooks/USERNAME/ADDRESSBOOKNAME?export
|
||||
https://example.com/remote.php/dav/addressbooks/USERNAME/ADDRESSBOOKNAME?export
|
||||
|
||||
Troubleshooting
|
||||
---------------
|
||||
|
||||
@@ -9,7 +9,7 @@ Calendar
|
||||
#. Select Add Account.
|
||||
#. Select Other as account type.
|
||||
#. Select Add CalDAV account.
|
||||
#. For server, type ``ADDRESS/remote.php/caldav/principals/username``
|
||||
#. For server, type ``example.com/remote.php/dav/principals/username``
|
||||
#. Enter your user name and password.
|
||||
#. Select Next.
|
||||
#. If your server does not support SSL, a warning will be displayed.
|
||||
@@ -34,7 +34,7 @@ Address book
|
||||
#. Select Add Account.
|
||||
#. Select Other as account type.
|
||||
#. Select Add CardDAV account.
|
||||
#. For server, type ``ADDRESS/remote.php/carddav/principals/username``
|
||||
#. For server, type ``example.com/remote.php/dav/principals/username``
|
||||
#. Enter your user name and password.
|
||||
#. Select Next.
|
||||
#. If your server does not support SSL, a warning will be displayed.
|
||||
@@ -52,4 +52,4 @@ Now should now find your contacts in the address book of your iPhone.
|
||||
If it's still not working, have a look at the :doc:`troubleshooting`
|
||||
and `Troubleshooting Contacts & Calendar`_ guides.
|
||||
|
||||
.. _Troubleshooting Contacts & Calendar: https://doc.owncloud.org/server/9.0/admin_manual/issues/index.html#troubleshooting-contacts-calendar
|
||||
.. _Troubleshooting Contacts & Calendar: https://doc.owncloud.org/server/9.0/admin_manual/issues/index.html#troubleshooting-contacts-calendar
|
||||
|
||||
@@ -3,23 +3,35 @@ Synchronizing with OS X
|
||||
|
||||
To use ownCloud with iCal you will need to use the following URL::
|
||||
|
||||
http://ADDRESS/remote.php/caldav/principals/username/
|
||||
https://example.com/remote.php/dav/principals/username/
|
||||
|
||||
The setup is basically the same as with iOS using the path **ADDRESS/remote.php/caldav/principals/username/** to sync with ownCloud. For OS X 10.7 Lion and 10.8 Mountain Lion everything works fine, but OS X 10.6 (Snow Leopard) and older needs some fiddling to work. A user contributed the following:
|
||||
The setup is basically the same as with iOS using the path ``https://example.com/remote.php/dav/principals/username/``
|
||||
to sync with ownCloud. For OS X 10.7 Lion and 10.8 Mountain Lion everything works
|
||||
fine, but OS X 10.6 (Snow Leopard) and older needs some fiddling to work. A user
|
||||
contributed the following:
|
||||
|
||||
#. Make sure, addressbook is not running. If it is, select the windows and press Command + Q to terminate it.
|
||||
#. Navigate to **/Users/YOUR\_USERNAME/Library/Application Support/AddressBook/Sources**. If you have all ready some kind of addressbook setup, it is likely you will see some folders named like this **BEA92826-FBF3-4E53-B5C6-ED7C2B454430**. Note down what folders there are now and leave the window open.
|
||||
#. Open addressbook and try to add a new CardDav addressbook. At this point, it does not matter what information you enter. It will come up with the same error message you mentioned before when you click "Create". Ignore it and click "Create" again. A non-functional addressbook will be added.
|
||||
#. Make sure, addressbook is not running. If it is, select the windows and press
|
||||
Command + Q to terminate it.
|
||||
#. Navigate to **/Users/YOUR\_USERNAME/Library/Application Support/AddressBook/Sources**.
|
||||
If you already have some kind of addressbook setup, it is likely you will see
|
||||
some folders named like this **BEA92826-FBF3-4E53-B5C6-ED7C2B454430**.
|
||||
Note down what folders there are now and leave the window open.
|
||||
#. Open addressbook and try to add a new CardDav addressbook. At this point, it
|
||||
does not matter what information you enter. It will come up with the same error
|
||||
message you mentioned before when you click "Create". Ignore it and click "Create"
|
||||
again. A non-functional addressbook will be added.
|
||||
#. Close addressbook again using Command + Q
|
||||
#. Go back to the folder window from step 2. You will now see a newly created folder with another long string as its name.
|
||||
#. Navigate to the newly created folder and edit the **Configuration.plist** with your favorite text editor.
|
||||
#. Go back to the folder window from step 2. You will now see a newly created folder
|
||||
with another long string as its name.
|
||||
#. Navigate to the newly created folder and edit the **Configuration.plist** with
|
||||
your favorite text editor.
|
||||
#. Search for a section looking like this::
|
||||
|
||||
<key>servername</key> <string>http://:0(null)</string> <key>username</key> <string>Whatever_you_entered_before</string>
|
||||
<key>servername</key> <string>https://:0(null)</string> <key>username</key> <string>Whatever_you_entered_before</string>
|
||||
|
||||
8. Make it look like this. Please note that the :80 after **YOUR_DOMAIN** is important::
|
||||
8. Make it look like this. Please note that the :443 after **example.com** is important::
|
||||
|
||||
<key>servername</key <string>http://YOUR_DOMAIN:80/owncloud/remote.php/carddav/principals/username</string> <key>username</key <string>username</string>
|
||||
<key>servername</key <string>https://example.com:443/owncloud/remote.php/dav/principals/username</string> <key>username</key <string>username</string>
|
||||
|
||||
9. Save the file and open addressbook again. It will not work yet.
|
||||
|
||||
@@ -33,5 +45,5 @@ If it's still not working, have a look at the :doc:`troubleshooting` and
|
||||
There is also an easy `HOWTO`_ in the forum.
|
||||
|
||||
|
||||
.. _HOWTO: http://forum.owncloud.org/viewtopic.php?f=3&t=132
|
||||
.. _HOWTO: https://forum.owncloud.org/viewtopic.php?f=3&t=132
|
||||
.. _Troubleshooting Contacts & Calendar: https://doc.owncloud.org/server/9.0/admin_manual/issues/index.html#troubleshooting-contacts-calendar
|
||||
|
||||
@@ -9,9 +9,9 @@ BlackBerry OS up to 10.2.2102 does not accept a URL with protocol ``https://``
|
||||
in front of the server address. It will always tell you that it cannot login on
|
||||
your server. So instead of writing::
|
||||
|
||||
https://address/remote.php/carddav/principals/username
|
||||
https://example.com/remote.php/dav/principals/username
|
||||
|
||||
in the server address field, you have to write::
|
||||
|
||||
address/remote.php/carddav/principals/username
|
||||
example.com/remote.php/dav/principals/username
|
||||
|
||||
Reference in New Issue
Block a user