Topic on User talk:GWicke

Hi,

regarding your change http://www.mediawiki.org/w/index.php?title=Parsoid/Troubleshooting&diff=0&oldid=797441 :

I think, my text (which you now have deleted) talking about the password-protected wiki is still relevant, because the Parsoid needs to know the password (this is my current thinking; I haven't tried it yet for my wikis). So, if there is a problem with the password, Parsoid and the Visiual Editor will not work.

And this should be mentioned as one of the possibilities on the Troubleshooting page.

Currently parsoid just forwards the cookie header (if set) to the wiki. If you are using VisualEditor, see the relevant configuration options for cookie forwarding in the VE extension.

Thanks.

I changed the text on that page, but can you please adapt it a second time, so that it then will probably be perfect?

I made it clear that no change on the Parsoid side is needed. All that is needed is to configure the VE extension properly.

Gabriel, I think, this change of Parsoid is really a big step forward. As soon as I have the time, I will try to deploy the latest version to all my protected wikis, some of them are using AuthPlugin in a Kerberos-authenticated intranet - where the VE/Parsoid currently could not be used.

I will report later, if it really works (I am confident, it will...)

-))

Great that it makes Parsoid more useful to you ;) In the foundation people were very happy when VE was enabled on a few internal wikis.

Note that when a cookie is set, we are sending no-cache headers for security reasons. In production most Parsoid output comes from the Parsoid Varnish caches, but private wikis are forced to be re-rendered for each request. Eventually we'll store HTML and do the access right checks at that layer. At that point private wikis will be fast too.