[users@httpd] Tracing redirects

[Dave Wreski <dw...@guardiandigital.com.INVALID>]

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 
with this redirect being created that it's impossible to trace. Do you 
have any tips on how to go about figuring this out?

Any ideas greatly appreciated.

Thanks,
Dave

Re: [users@httpd] Tracing redirects

[Frank Gingras <th...@apache.org>]

On Sat, Feb 24, 2024 at 12:18 PM Alec Burgess <bu...@gmail.com> wrote:

> Alec Burgess passed away please remove home from your mailing list
>
> Regards Pattie
> Regards ... Alec
> --
>
>
> On Fri, Nov 24, 2023 at 8:24 PM Will Fatherley <we...@gmail.com>
> wrote:
>
>>
>>
>>> - 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 :)
>
>
Condolences, but you must do that on your end, see the instructions on:

https://httpd.apache.org/userslist.html

Re: [users@httpd] Tracing redirects

[Alec Burgess <bu...@gmail.com>]

Alec Burgess passed away please remove home from your mailing list

Regards Pattie
Regards ... Alec
--


On Fri, Nov 24, 2023 at 8:24 PM Will Fatherley <we...@gmail.com>
wrote:

>
>
>> - 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 :)

Re: [users@httpd] Tracing redirects

[Will Fatherley <we...@gmail.com>]

>
> - 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 :)

Re: [users@httpd] Tracing redirects

[Will Fatherley <we...@gmail.com>]

> 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 client on the first url, and write the location header to file or
stdout each time your 3xx response comes through

>