Mantis Bugtracker

Viewing Issue Simple Details Jump to Notes ] View Advanced ] Issue History ] Print ]
ID Category Severity Reproducibility Date Submitted Last Update
0002395 [Resin] minor always 02-04-08 09:10 02-13-08 15:41
Reporter sam View Status public  
Assigned To ferg
Priority urgent Resolution fixed  
Status closed   Product Version 3.1.4
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:

    <moved-permanently regexp="http://some.old.domain/path" [^] target="..."/>
Additional Information
Attached Files

- Relationships

- Notes
02-13-08 15:41


- Issue History
Date Modified Username Field Change
02-04-08 09:10 sam New Issue
02-13-08 09:37 ferg Status new => acknowledged
02-13-08 15:41 ferg Note Added: 0002772
02-13-08 15:41 ferg Assigned To  => ferg
02-13-08 15:41 ferg Status acknowledged => closed
02-13-08 15:41 ferg Resolution open => fixed
02-13-08 15:41 ferg Fixed in Version  => 3.1.5

Mantis 1.0.0rc3[^]
Copyright © 2000 - 2005 Mantis Group
29 total queries executed.
26 unique queries executed.
Powered by Mantis Bugtracker