266 | | === Using apache rewrite rules === |
267 | | In some situations when you choose to use tracd behind apache, you might experience issues with redirects, like being redirected to URLs with the wrong host or protocol. In this case (and only in this case), setting the `[trac] use_base_url_for_redirect` to `true` can help, as this will force Trac to use the value of `[trac] base_url` for doing the redirects. |
| 266 | === Using tracd behind a proxy |
| 267 | |
| 268 | In some situations when you choose to use tracd behind Apache or another web server. |
| 269 | |
| 270 | In this situation, you might experience issues with redirects, like being redirected to URLs with the wrong host or protocol. In this case (and only in this case), setting the `[trac] use_base_url_for_redirect` to `true` can help, as this will force Trac to use the value of `[trac] base_url` for doing the redirects. |
| 271 | |
| 272 | If you're using the AJP protocol to connect with `tracd` (which is possible if you have flup installed), then you might experience problems with double quoting. Consider adding the `--unquote` parameter. |
| 273 | |
| 274 | See also [trac:TracOnWindowsIisAjp], [trac:TracNginxRecipe]. |