|
Mantis - Resin
|
|||||
| Viewing Issue Advanced Details | |||||
|
|
|||||
| ID: | Category: | Severity: | Reproducibility: | Date Submitted: | Last Update: |
| 2395 | minor | always | 02-04-08 09:10 | 02-13-08 15:41 | |
|
|
|||||
| Reporter: | sam | Platform: | |||
| Assigned To: | ferg | OS: | |||
| Priority: | urgent | OS Version: | |||
| Status: | closed | Product Version: | 3.1.4 | ||
| Product Build: | Resolution: | fixed | |||
| Projection: | none | ||||
| ETA: | none | Fixed in Version: | 3.1.5 | ||
|
|
|||||
| Summary: | 0002395: rewrite-dispatch rules at <server> level do not get logged | ||||
| Description: |
(rep by D Peterson) We have some <rewrite-dispatch/> rules defined at the <server/> level so that they are applied across all virtual hosts and web-apps and I noticed that requests that hit these rules don't get logged. We also have some app-specific rules defined in <web-app/> and those requests are logged - we see the 301 or 302 response code logged out along with the request URI. I tried moving the rewrite rules into a host-default block, but then they stopped matching (probably because the regex has absolute URLs so we can catch the hostname). For example: <rewrite-dispatch> <moved-permanently regexp="http://some.old.domain/path" [^] target="..."/> </rewrite-dispatch> |
||||
| Steps To Reproduce: | |||||
| Additional Information: | |||||
| Relationships | |||||
| Attached Files: | |||||
| Notes | |||||
|
|
|||||
|
|
||||