When a backslash is appended to the url for our RT 3.6.7 site (running
with Perl 5.10.0), RT tosses a system error, which exposes information
about where we’ve installed Perl and RT and their versions. Is this
fixed in 3.8.X? If not, is a fix forthcoming? Thanks
Here’s the error, with paths changed:
System error
error: could not find component for initial path '/' (component roots
are: ‘/path_to_rt/local/html’, ‘/path_to_rt/share/html’)
context:
…
207: $self->{out_method} = sub { $$bufref .= $_[0] };
208: }
209: $self->{use_internal_component_caches} =
210: $self->{interp}->use_internal_component_caches;
211: $self->_initialize;
212:
213: return $self;
214: }
215:
…
code stack: /path_to_perl/lib/site_perl/5.10.0/HTML/Mason/Request.pm:211
/path_to_perl/lib/site_perl/5.10.0/Class/Container.pm:275
/path_to_perl/lib/site_perl/5.10.0/Class/Container.pm:353
/path_to_perl/lib/site_perl/5.10.0/HTML/Mason/Interp.pm:348
/path_to_perl/lib/site_perl/5.10.0/HTML/Mason/Interp.pm:342
/path_to_perl/lib/site_perl/5.10.0/HTML/Mason/CGIHandler.pm:121
/path_to_perl/lib/site_perl/5.10.0/HTML/Mason/CGIHandler.pm:73
/path_to_rt/bin/mason_handler.fcgi:78
raw error
Karl Boyken
Karl Boyken, system administrator
karl-boyken@uiowa.edu
303A MLH, Dept. of Comp. Sci.
http://www.cs.uiowa.edu/~boyken/
The U. of Iowa, Iowa City, IA 52242 319-335-2730 (voice)
319-335-3668 (fax)
smime.p7s (3.19 KB)
$LogToScreen in RT_SiteConfig
Fix has existed as long as I have administered RT (3.2)
Karl Boyken wrote:
When a backslash is appended to the url for our RT 3.6.7 site (running
with Perl 5.10.0), RT tosses a system error, which exposes information
about where we’ve installed Perl and RT and their versions. Is this
fixed in 3.8.X? If not, is a fix forthcoming? Thanks
Here’s the error, with paths changed:
System error
error: could not find component for initial path '/' (component
roots are: ‘/path_to_rt/local/html’, ‘/path_to_rt/share/html’)
context:
…
207: $self->{out_method} = sub { $$bufref .= $_[0] };
208: }
209: $self->{use_internal_component_caches} =
210: $self->{interp}->use_internal_component_caches;
211: $self->_initialize;
212:
213: return $self;
214: }
215:
…
code stack:
/path_to_perl/lib/site_perl/5.10.0/HTML/Mason/Request.pm:211
/path_to_perl/lib/site_perl/5.10.0/Class/Container.pm:275
/path_to_perl/lib/site_perl/5.10.0/Class/Container.pm:353
/path_to_perl/lib/site_perl/5.10.0/HTML/Mason/Interp.pm:348
/path_to_perl/lib/site_perl/5.10.0/HTML/Mason/Interp.pm:342
/path_to_perl/lib/site_perl/5.10.0/HTML/Mason/CGIHandler.pm:121
/path_to_perl/lib/site_perl/5.10.0/HTML/Mason/CGIHandler.pm:73
/path_to_rt/bin/mason_handler.fcgi:78
raw error
Karl Boyken
The rt-users Archives
Community help: http://wiki.bestpractical.com
Commercial support: sales@bestpractical.com
Discover RT’s hidden secrets with RT Essentials from O’Reilly Media.
Buy a copy at http://rtbook.bestpractical.com
Drew Barnes
Applications Analyst
Network Resources Department
Raymond Walters College
University of Cincinnati
When a backslash is appended to the url for our RT 3.6.7 site (running
with Perl 5.10.0), RT tosses a system error, which exposes information
about where we’ve installed Perl and RT and their versions. Is this
fixed in 3.8.X?
Yes, there’s now a 404 page.
As other users point out, there are other ways to deal with this.
Interesting–it does not work. I tried setting $LogToScreen to undef,
‘emergency’, and 0, but the error still displays on the screen. (I’m
cleaning out the mason cache and restarting httpd.)
Karl Boyken
Drew Barnes wrote:
$LogToScreen in RT_SiteConfig
Fix has existed as long as I have administered RT (3.2)
Karl Boyken wrote:
When a backslash is appended to the url for our RT 3.6.7 site (running
with Perl 5.10.0), RT tosses a system error, which exposes information
about where we’ve installed Perl and RT and their versions. Is this
fixed in 3.8.X? If not, is a fix forthcoming? Thanks
Here’s the error, with paths changed:
System error
error: could not find component for initial path '/' (component
roots are: ‘/path_to_rt/local/html’, ‘/path_to_rt/share/html’)
context: … 207: $self->{out_method} = sub { $$bufref .=
$_[0] };
208: }
209: $self->{use_internal_component_caches} =
210: $self->{interp}->use_internal_component_caches;
211: $self->_initialize;
212: 213: return $self;
214: }
215: … code stack:
/path_to_perl/lib/site_perl/5.10.0/HTML/Mason/Request.pm:211
/path_to_perl/lib/site_perl/5.10.0/Class/Container.pm:275
/path_to_perl/lib/site_perl/5.10.0/Class/Container.pm:353
/path_to_perl/lib/site_perl/5.10.0/HTML/Mason/Interp.pm:348
/path_to_perl/lib/site_perl/5.10.0/HTML/Mason/Interp.pm:342
/path_to_perl/lib/site_perl/5.10.0/HTML/Mason/CGIHandler.pm:121
/path_to_perl/lib/site_perl/5.10.0/HTML/Mason/CGIHandler.pm:73
/path_to_rt/bin/mason_handler.fcgi:78
raw error
Karl Boyken
The rt-users Archives
Community help: http://wiki.bestpractical.com
Commercial support: sales@bestpractical.com
Discover RT’s hidden secrets with RT Essentials from O’Reilly Media.
Buy a copy at http://rtbook.bestpractical.com
Karl Boyken, system administrator
karl-boyken@uiowa.edu
303A MLH, Dept. of Comp. Sci.
http://www.cs.uiowa.edu/~boyken/
The U. of Iowa, Iowa City, IA 52242 319-335-2730 (voice)
319-335-3668 (fax)
smime.p7s (3.19 KB)
On my production box (3.6.5), the backslash just returns a blank page with
Not Found
The requested URL /\ was not found on this server.On my dev box (3.8.1) I get the side menu bar, top menu bars, and (in the main content area) The page you requested could not be found Please check the URL and try again. The line in my RT_SiteConfig on both boxes is Set($LogToScreen, undef); I notice that on my 3.6.5 box, the default for $LogToScreen in RT_Config is error while on my 3.8.1 it is info. Sorry I can’t provide more help. Do you have a vanilla test box to try this on? Karl Boyken wrote:
Interesting–it does not work. I tried setting $LogToScreen to undef,
‘emergency’, and 0, but the error still displays on the screen. (I’m
cleaning out the mason cache and restarting httpd.)
Karl Boyken
Drew Barnes wrote:
$LogToScreen in RT_SiteConfig
Fix has existed as long as I have administered RT (3.2)
Karl Boyken wrote:
When a backslash is appended to the url for our RT 3.6.7 site
(running with Perl 5.10.0), RT tosses a system error, which exposes
information about where we’ve installed Perl and RT and their
versions. Is this fixed in 3.8.X? If not, is a fix forthcoming?
Thanks
Here’s the error, with paths changed:
System error
error: could not find component for initial path '/'
(component roots are: ‘/path_to_rt/local/html’,
‘/path_to_rt/share/html’)
context: … 207: $self->{out_method} = sub { $$bufref
.= $_[0] };
208: }
209: $self->{use_internal_component_caches} =
210: $self->{interp}->use_internal_component_caches;
211: $self->_initialize;
212: 213: return $self;
214: }
215: … code stack:
/path_to_perl/lib/site_perl/5.10.0/HTML/Mason/Request.pm:211
/path_to_perl/lib/site_perl/5.10.0/Class/Container.pm:275
/path_to_perl/lib/site_perl/5.10.0/Class/Container.pm:353
/path_to_perl/lib/site_perl/5.10.0/HTML/Mason/Interp.pm:348
/path_to_perl/lib/site_perl/5.10.0/HTML/Mason/Interp.pm:342
/path_to_perl/lib/site_perl/5.10.0/HTML/Mason/CGIHandler.pm:121
/path_to_perl/lib/site_perl/5.10.0/HTML/Mason/CGIHandler.pm:73
/path_to_rt/bin/mason_handler.fcgi:78
raw error
Karl Boyken
The rt-users Archives
Community help: http://wiki.bestpractical.com
Commercial support: sales@bestpractical.com
Discover RT’s hidden secrets with RT Essentials from O’Reilly Media.
Buy a copy at http://rtbook.bestpractical.com
Drew Barnes
Applications Analyst
Network Resources Department
Raymond Walters College
University of Cincinnati
On my production box (3.6.5), the backslash just returns a blank page with
Not Found
The requested URL /\ was not found on this server.
That’s because you have apache matching specific files rather than
“everything under /”