Due to pending manifest v3 changes coming to Chromium based browsers, we are attempting to switch to Firefox. Unfortunately there are some bugs I’ve been unable to resolve when using XWiki in Firefox. XWiki works without error in both Chrome and Edge, but in Firefox I was getting the dreaded Failed to lock page error. Our XWiki installation is running in a Docker container behind an Nginx reverse proxy. We have a dozen services running in Docker containers behind this reverse proxy with no issue, but I made sure all our settings were in line with this documentation, and tried all the suggestions mentioned in this thread, all to no avail. Though not optimal, I eventually set edit.document.inPlaceEditing.enabled = false to work around this particular issue.
The next issue is that I am unable to create new pages in Firefox, getting the error Error while transforming the page title to a correct page name: the exact page title will be used.
This error appears immediately when anything is typed into the “Title” box, and it disables the “Create” button, making it impossible to create new pages in Firefox.
I believe both of the issues I’ve mentioned have the same underlying problem, I just don’t know why. When opening the DevTools in both Chrome and Firefox then comparing the “Network” tab entries when the same interactions are made in the XWiki, Firefox eventually results in a network request which returns a status of 302, followed by another network request which returns a status of 401. The exact same action in Chrome results in a network request which returns a status of 200. It doesn’t matter what the interaction is, the general pattern is always the same.
Extending the example for which I provided a picture, as soon as a single letter is typed in the “Title” box both Chrome and Firefox hit the same URL, however Chrome uses an XHR request whereas Firefox uses an HTML request. The URL:
https://xwiki.example.com/bin/get/Main/?xpage=entitynamevalidation_json&outputSyntax=plain&name=a&form_token=Zyx2KrFQRaYkyXxtWwhfnx
In Chrome the XHR GET request returns with a 200 status, the exact same request is repeated with the same result (unclear why, but not an issue), and no further requests are made.
In Firefox the HTML GET request returns with a 302 status, then a request to the XWiki login screen is made which returns with a 401 status, then both of those requests are repeated with the same result. The URL for the request that returns a 401 status:
https://xwiki.example.com/bin/login/XWiki/XWikiLogin;jsessionid=368FED311E78CAB481019B052CDB9C20?srid=bxaBWSzC&xredirect=%2Fbin%2Fget%2FMain%2F%3Fxpage%3Dentitynamevalidation_json%26outputSyntax%3Dplain%26name%3Da%26form_token%3DYyx2KrFQRaYkyXxtWwhfnw%26srid%3DbxaBWSzC
The login page doesn’t render, and I’m not redirected, but I can see in the XWiki login page is returned in the response to the request. Even after this happens, I’m still logged in to XWiki and can navigate to other pages and other such things.
This isn’t an issue with one Firefox install, it is all of them, including the mobile browser. I’ve disabled all Firefox security settings during testing just to see what could be causing this, but so far I’ve been unable to find the culprit. Any guidance would be appreciated.
3 posts - 2 participants