2-1-72 errors

In /usr/local/rt3/share/html/Ticket/Elements/AddWatchers

$GroupString is not explicitly defined…

Adding $GroupString => undef to the <%ARGS> fixes the error.

The search function in index.html displays a 200 page with document has
moved, instead of doing a 403 (Document has moved) to actually redirect you
to the page (Assuming it’s supposed to redirect you).

Thanks,

Derek

Err… on 2) s/403/302/

Derek----- Original Message -----
From: Derek Buttineau
To: rt-devel@lists.fsck.com
Sent: Monday, February 17, 2003 10:24 AM
Subject: [rt-devel] 2-1-72 errors

In /usr/local/rt3/share/html/Ticket/Elements/AddWatchers

$GroupString is not explicitly defined…

Adding $GroupString => undef to the <%ARGS> fixes the error.

The search function in index.html displays a 200 page with document has
moved, instead of doing a 403 (Document has moved) to actually redirect you
to the page (Assuming it’s supposed to redirect you).

Thanks,

Derek

rt-devel mailing list
rt-devel@lists.fsck.com
http://lists.fsck.com/mailman/listinfo/rt-devel

In /usr/local/rt3/share/html/Ticket/Elements/AddWatchers

$GroupString is not explicitly defined…

Adding $GroupString => undef to the <%ARGS> fixes the error.

nod Should be fixed in 2.1.73

The search function in index.html displays a 200 page with document has
moved, instead of doing a 403 [302] (Document has moved) to actually redirect you
to the page (Assuming it’s supposed to redirect you).

Can you back this up with a packet sniff or dump? With both fastcgi and
mod_perl, I’m seeing an HTTP/1.1 302 Moved.

Best,
Jesse

Thanks,

Derek


rt-devel mailing list
rt-devel@lists.fsck.com
http://lists.fsck.com/mailman/listinfo/rt-devel

�|� http://www.bestpractical.com/rt – Trouble Ticketing. Free.

Can you back this up with a packet sniff or dump? With both fastcgi and
mod_perl, I’m seeing an HTTP/1.1 302 Moved.

It’s using apache2/mod_perl2 so that may be the cause of it.

It basically just takes me to a page with the HTML:

200 OK

OK

The document has moved here.


Apache/2.0.43 Server at rt2.csolve.net Port 80

Clicking the link completes the redirection and from that point the search
does work properly. It may perhaps be a bug in mod_perl2?

Derek

Can you back this up with a packet sniff or dump? With both fastcgi and
mod_perl, I’m seeing an HTTP/1.1 302 Moved.

It’s using apache2/mod_perl2 so that may be the cause of it.

It basically just takes me to a page with the HTML:

Right. but what I need is the HTTP headers, not the html. This may well
be a bug in apache2/mod_perl2. Which I still don’t trust or recommend
anyone use in production.

�|� http://www.bestpractical.com/rt – Trouble Ticketing. Free.

It basically just takes me to a page with the HTML:

Right. but what I need is the HTTP headers, not the html. This may well
be a bug in apache2/mod_perl2. Which I still don’t trust or recommend
anyone use in production.

This might shed a little light:

http://marc.theaimsgroup.com/?l=apache-modperl&m=102162397305385&w=2

Looks like HTML::Mason::Request::ApacheHandler::redirect() doesn’t play
nice with Apache 2.

Chris Reinhardt
ctriv@dyndns.org
Systems Architect
Dynamic DNS Network Services
http://www.dyndns.org/