>
> - use a client on the first url, and write the location header to file or
> stdout each time your 3xx response comes through
>
>> … using a script that has access to a set data structure that can store
each request url, so as to break before the second request to the first
resource :)
> Any ideas greatly appreciated.
>
Probably a good idea to think of a longer term vision for logging approach,
but the two other possibilities I can think of are
- awk grep or sed your configuration files with some desirable regular
expression to include the rewrite directives and rules
- use a
Hi,
I have a link on our site that is caught in a redirect loop that I can't
figure out. We have a few thousand redirects, making it very difficult
to track down.
I've tried enabling logging:
LogLevel info rewrite:trace2
but even with just trace2, there are thousands of log lines associated
