Bug: mod_perl 1.99 (ie RHEL3) breaks ALLOWWEBVIEW
with mod_perl, ALLOWWEBVIEW causes a twikiweb to become write-only with no read access
Test case
- Set up TWiki with called perl (not mod_perl) -- basic authentication
- create a twikiweb
- in that web set ALLOWWEBVIEW to your wikiname
- see that you can view that web
- change apache to use mod_perl
- access that web (log in correctly)
- then move to several different topics in that web.
Eventually (after two or three different topics for me) you can't access any topic in that twikiweb. However, if you change back from mod_perl to called perl and restart httpd you can access everything correctly.
If you can copy/paste or just type in a URL to edit any topic in that twikiweb, you can access the edit page. You just can't view the page, hence the write-only description, as
CrawfordCurrie put it on irc.
RafaelAlvarez asked me to slightly adjust TWiki/UI/View.pm on line 250 by adding at the end of the if another "or":
if( (!$topicExists) || $TWiki::readTopicPermissionFailed || !$viewAccessOK) {
No change in behaviour. I can click on two topics after logging in before I lose access. If I close the browser and open it up again I can log in and see just WebHome. Topics off that page are all access denied. If I close out the browser again and open it again I don't even get asked to login. The only way I can get it back to being able to view the two pages again is by restarting httpd.
Environment
| TWiki version: |
TWikiRelease01Sep2004 |
| TWiki plugins: |
whatever came with Cairo |
| Server OS: |
CentOS 3.3 (like RHEL3) |
| Web server: |
2.0.46-40 |
| Perl version: |
5.8.0-88.7 |
| Client OS: |
Windows XP SP2 |
| Web Browser: |
IE 6 sp2 |
--
ScottSibert - 19 Nov 2004
Follow up
Fix record