Skip to content

Commit

Permalink
Private pads description update
Browse files Browse the repository at this point in the history
Hi,
I just made clear that HTTPS is needed to run Etherpad with Nextcloud and private pads through the API.

I realized that in DisplayController.php line 95, we have setcookie() with the HTTPS only parameter set. I running all locally and I wondering why Etherpad couldn't grant me access to pads, and It was because the session ID was not being sent.

Thank you for your work! 😄
  • Loading branch information
filisko committed Feb 11, 2019
1 parent 1f16537 commit 6e2c596
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion README.md
Expand Up @@ -67,7 +67,7 @@ example, you’ll have to set the cookie domain to `example.org` within
the Ownpad settings.

If you want to create *truly* private pads, you have to dedicate an
Etherpad instance for Nextcloud. You will then configure Etherpad to
Etherpad instance for Nextcloud **running both with HTTPS**. You will then configure Etherpad to
restrict pad access via sessions and pad creation via the API.
For this, you have to adjust your Etherpad configuration file
(`settings.json`) as following:
Expand Down

0 comments on commit 6e2c596

Please sign in to comment.