Home/ Questions/Q 6105361
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-23T13:57:59+00:00

EDIT: the IIRF.ini code was not the problem in this case, the performance issues

  • 0

EDIT: the IIRF.ini code was not the problem in this case, the performance issues with dokuwiki were in fact permissions related, and the introduction of URL re-writing was not the cause of the issue.

I’ve got a new instance of Dokuwiki (i.e. almost empty, not in use) which was running perfectly fine, before I integrated URL-rewriting using IIRF.

It now runs significantly more slowly – navigating between pages takes a number of seconds whereas before it was ‘snappy’ (immediate).

I followed the directions for implementing IIRF here, which basically involves adding an “IIRF.ini” file to the site root, and updating the “conf/local.php” file as instructed on the site linked above (code copied from under the heading “Ionics Isapi Rewrite Filter”).

So to clarify, URL-rewriting is working; but it’s caused significant slow-down in navigating the wiki. I’d appreciate it if anyone could offer a suggestion for bringing it up to speed again!

This is the contents of my “IIRF.ini” file:

IterationLimit 1

# QSA is not supported, fix it
RewriteCond %{REQUEST_FILENAME}       !-f
RewriteCond %{REQUEST_FILENAME}       !-d
RewriteRule (.*)\?(.*) $1&$2

RewriteRule ^/_media/(.*)             /lib/exe/fetch.php?media=$1   [QSA,L]
RewriteRule ^/_detail/(.*)            /lib/exe/detail.php?media=$1  [QSA,L]
RewriteRule ^/_export/([^/]+)/(.*)    /doku.php?do=export_$1&id=$2  [QSA,L]
RewriteRule ^/$                       /doku.php                     [QSA,L]

# infinite redirect fix
RewriteCond %{REQUEST_FILENAME}       !-d
RewriteRule ^/(.*)/$                  /doku.php?id=$1               [QSA,L]

# end fix
RewriteCond %{REQUEST_FILENAME}       !-f
RewriteCond %{REQUEST_FILENAME}       !-d
RewriteRule ^/(.*)                    /doku.php?id=$1               [QSA,L]
Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    Not an an answer but some suggestions:

    1. Do you know if it’s a specific rule that’s causing the problem or IIRF itself? Comment out all the rukes and try just the following:

      RewriteRule ^(*.) $1

      To test IIRF prformance then uncomment other rules.

    2. Switch on tracing. Are the rules behaving as expected?

    3. Use the TestDriver application to run your tests.

    4. Try to run your tests in the context of the user your web server software uses.

    My guess is that there is an access issue on a file or directory test.

    • 0