dispatch.fcgi gets called and mod_fcgid executes it. The rewrite rule is necessary, because otherwise /media/bla is resolved to /dispatch.fcgi/media/bla which will fail.

And where does dispatch.fcgi come from? How is our Django fastcgi script ever executed? At some point our code needs to run and I don't see the magic here that lets that happen.

Sorry, I meant reviewboard.fcgi.

Okay. I'm still missing the part where we actually reference reviewboard.fcgi. We have the one entry for mod_fastcgi, but not for mod_fcgid.

Files with .fcgi extension are handled by mod_fcgid. I really don't know exactly why mod_fastcgi needs additional configuration and mod_fcgid doesn't...

Well, mod_fcgid can't just guess where reviewboard.fcgi lives, so it absolutely has to reference it somewhere. Does it reuse the FastCGIServer line? If so, then we need to make sure we specify that for both modules (and make sure it doesn't conflict when both are enabled).

Well, the root folder (htdocs) contains reviewboard.fcgi, so it doesn't need to guess. mod_fcgid doesn't understand the FastCGIServer option. If you have both modules loaded it won't work, but that wouldn't really make sense anyway.

I was looking primarily at your changes and completely missed that it's just reusing that RewriteRule at the bottom. My apologies, I think I was up too late last night.