Question

I found the answer know, so I'll just post this question/problem if you run into it.

If using the ActionTrackerPlugin with more than 10 entries on a page, it would not save any edits. Still the version number would increase, but the old content stayed on the page (is it called Topic?)

If the Twiki server was called directly from a browser (not going through the reverse proxy machine) it would gladly save all edits. Thus if the Twiki server was reached from the intranet side, it could create a page with 11 action entries but that page could not be edited any more from the outside/Internet as that connection was done through the reverse proxy machine and the page now contained to many Actions for a save to work.

No errors of any kind showed up in the apache logs on both machines. All authentication mechanisms were tried as well.

You can live with less than 10 Actions on a page, so it was not a major crises until I noticed the same problem of unsaved edits on other pages as well. Not all, but some pages could not be correctly edited and saved.

I used encryped HTTPS:// communication on all lines, between browser and reverse proxy and between reverseproxy and twiki server. (Needed as the http/https URLs seems to not work correctly in all the perl scripts, i.e internal page links will point you to a http connection even if you are using https from the internet)

Environment

-- AndersHedberg - 08 Nov 2006

Answer

If you answer a question - or someone answered one of your questions - please remember to edit the page and set the status to answered. The status selector is below the edit box.

The problem was not with the Twiki but with Apache, the original reverse proxy was running apache 2.0.55 on Windows, after an update to version 2.2.3 (windows) it is working correctly and all topics can be edited and saved. (My TWiki is running on linux in a Vmvare machine (see there version of twiki it's superb!, and the reverse proxy server is running Windows XP in another vmware machine)

So if you run into this problem, update the reverse proxy apache machine.

-- AndersHedberg - 08 Nov 2006