One more thing I forgot to add is that I can never access /NoAuth/ on the same port as the RT application itself, it always returns me to the login screen and gives a page not found error.
e.g. https://rthost.tld:8383/NoAuth/images/ Gives me an RT-generated "The page you requested could not be found | Please check the URL and try again" page. In the process of troubleshooting this NoAuth page problem I've setup a vhost for the NoAuth pages, which is where they don't execute. I'm quite certain this is a simple matter but I"ve been having a difficult time with it. What should the directives in Apache's httpd.conf look like for proper access to pages under /NoAuth/ directories? On Thu, Mar 4, 2010 at 3:41 PM, Zuckercorn, Barry <[email protected]> wrote: > I have done some additional troubleshooting and am still hitting a bit > of a snag. > > I have pages created on our 3.6 RT install (apache 1.3) that read > similar to this: > > ...mumble... > > <TABLE WIDTH=98% CELLSPACING=2 CELLPADDING=5 border=2> > <%PERL> > my $tickets = new RT::Tickets($user); > $tickets->LimitQueue(VALUE => 'QUEUENAME'); > $tickets->LimitStatus(VALUE => 'open'); > $tickets->LimitStatus(VALUE => 'new'); > $tickets->OrderBy(FIELD => 'id', ALIAS => 'main', ORDER => 'DESC'); > </%PERL> > % if ($tickets->Count) { > > .... mumble mumble.... > > <%INIT> > my $user = new RT::CurrentUser('guest'); > my $queue = new RT::Queue($user); > my $i=0; > my $restrict; > </%INIT> > > > This allows a user in our helpdesk to view a page of open issues in > this particular example. We authenticate them via htaccess/htpasswd > and just let them cruise a page of open issues because we don't want > to expose the contents of the tickets to anyone that isn't a user in > the system. > > I'm open to suggestions on other ways of handling this but this is the > way it has been done historically but our 3.8 install doesn't seem to > like it. It doesn't actually execute any of the %PERL glue and just > spits it out into the contents of the page. I am not sure if this is > an Apache configuration issue, an RT configuration issue, or both. > > I do have mod_perl activated in httpd.conf and we are using fastcgi > and mason_handler.fcgi for the application itself. > > In httpd.conf I have been trying out various directives but this is > what it looks like as of now for /NoAuth: > > <Location /NoAuth> > satisfy any > SetHandler perl-script > PerlOptions +ParseHeaders > Options +ExecCGI > allow from all > </Location> > _______________________________________________ http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users Community help: http://wiki.bestpractical.com Commercial support: [email protected] 2010 RT Training Sessions! San Francisco, CA, USA - Feb 22 & 23 Dublin, Ireland - Mar 15 & 16 Boston, MA, USA - April 5 & 6 Washington DC, USA - Oct 25 & 26 Discover RT's hidden secrets with RT Essentials from O'Reilly Media. Buy a copy at http://rtbook.bestpractical.com
