Redirects On SuSE 9.1

I realize this is more of an Apache2 question (and we have looked through the Apache2 docs some already, to no avail), but I thought that someone else here may have solved this identical problem. We have a brand new OTRS 1.2.4 installation on a new SuSE 9.1 server with Apache2. (This is our first SuSE 9.1/Apache2 production installation). To access OTRS, we find that users must enter "http://serverFQDN/otrs/index.pl" in their web browsers. If they enter "http://serverFQDN/otrs/" they get a 404 Object Not Found error. It seems as if the file /opt/otrs/var/httpd/htdocs/index.html doesn't redirect the user successfully. Ideally, we would like users to enter only "http://serverFQDN/otrs" (without the trailing slash) if possible, but we'll settle for just getting this redirect to work. Thanks! Mark -- _________________________________________________ L. Mark Stone Reliable Networks of Maine, LLC 477 Congress Street Portland, ME 04101 Tel: (207) 772-5678

On Sunday, September 05, 2004 5:39 PM
L. Mark Stone
To access OTRS, we find that users must enter "http://serverFQDN/otrs/index.pl" in their web browsers. If they enter "http://serverFQDN/otrs/" they get a 404 Object Not Found error.
See: /opt/otrs/scripts/apache2-httpd.include.conf Set: ErrorDocument 403 /otrs/index.pl And: DirectoryIndex index.pl
It seems as if the file /opt/otrs/var/httpd/htdocs/index.html doesn't redirect the user successfully.
index.html is just a last resort. With kind regards, Robert Kehl

On Wednesday, September 8, 2004 03:46 am, Robert Kehl wrote:
On Sunday, September 05, 2004 5:39 PM
L. Mark Stone
wrote: To access OTRS, we find that users must enter "http://serverFQDN/otrs/index.pl" in their web browsers. If they enter "http://serverFQDN/otrs/" they get a 404 Object Not Found error.
See: /opt/otrs/scripts/apache2-httpd.include.conf
Set: ErrorDocument 403 /otrs/index.pl
The error document as above was already set.
And: DirectoryIndex index.pl
I added this statement.
It seems as if the file /opt/otrs/var/httpd/htdocs/index.html doesn't redirect the user successfully.
index.html is just a last resort.
With kind regards,
Robert Kehl
No joy Robert, the user still has to enter the full path including the index.pl file to log in. I of course restarted Apache. Unless you have something else we should try, I guess we will wait for 1.3... Danke, Mark -- _________________________________________________ L. Mark Stone Reliable Networks of Maine, LLC 477 Congress Street Portland, ME 04101 Tel: (207) 772-5678 ************************************************ * Please note that my cell number has changed! * * The new number is (207) 615-1529 * * The old number will be retired by Sept 15th. * ************************************************

On Wednesday, September 08, 2004 11:04 PM
L. Mark Stone
L. Mark Stone
wrote: To access OTRS, we find that users must enter "http://serverFQDN/otrs/index.pl" in their web browsers. If they enter "http://serverFQDN/otrs/" they get a 404 Object Not Found error.
Then see your logs, about which file does Apache complain? With kind regards, Robert Kehl

On Wednesday, September 8, 2004 08:22 pm, Robert Kehl wrote:
On Wednesday, September 08, 2004 11:04 PM
L. Mark Stone
wrote: L. Mark Stone
wrote: To access OTRS, we find that users must enter "http://serverFQDN/otrs/index.pl" in their web browsers. If they enter "http://serverFQDN/otrs/" they get a 404 Object Not Found error.
Then see your logs, about which file does Apache complain?
When I type http://inside.rnome.com/otrs/ in a web browser, /var/log/apache2/error.log shows: [error] [client 24.97.161.122] Attempt to serve directory: /opt/otrs/bin/cgi-bin/ I hope this is helpful in tracking the problem down. Thanks, Mark -- _________________________________________________ L. Mark Stone Reliable Networks of Maine, LLC 477 Congress Street Portland, ME 04101 Tel: (207) 772-5678 ************************************************ * Please note that my cell number has changed! * * The new number is (207) 615-1529 * * The old number will be retired by Sept 15th. * ************************************************

On Thursday, September 09, 2004 8:24 PM
L. Mark Stone
When I type http://inside.rnome.com/otrs/ in a web browser, /var/log/apache2/error.log shows:
[error] [client 24.97.161.122] Attempt to serve directory: /opt/otrs/bin/cgi-bin/
I hope this is helpful in tracking the problem down.
Yes, I remember now, it has something to do with Apache not being able
assigning the DirectoryIndex due to the perl-script handler being first.
Well, there are several ways, as always. You could use s.th. brutal like
this:
ErrorDocument 404 /otrs/index.pl
More elegant is to make use of mod_rewrite:
RewriteEngine On
RewriteRule ^/otrs$ /otrs/
RewriteRule ^/otrs/$ /index.pl [R,L]
Or:
RewriteEngine On
RewriteBase /otrs/
RewriteRule ^/otrs$ /otrs/
RewriteRule ^/otrs/$ /index.pl [R,L]
At last, or if mod_rewrite is no choice, one might think about changing
the <Location> container in apache2-httpd-include.conf in such a way the
perl-handler won't jump in when we want the DirectoryIndex option to
become active. A working apache2-http-include.conf would then look like
this:
# OTRS
Alias /otrs/ "/opt/otrs/bin/cgi-bin/"
Alias /otrs-web/ "/opt/otrs/var/httpd/htdocs/"
<IfModule mod_perl.c>
Perlrequire /opt/otrs/scripts/apache2-perl-startup.pl
</IfModule>

On Thursday, September 9, 2004 04:25 pm, Robert Kehl wrote:
Yes, I remember now, it has something to do with Apache not being able assigning the DirectoryIndex due to the perl-script handler being first.
Robert,
I tried incorporating your suggestions by editing the existing otrs.conf file
in the /etc/apache2/conf.d directory. After restarting Apache2,
unfortunately, http://site/otrs and http://site/otrs/ still don't work.
Probably I missed something, so here's the otrs conf file. Perhaps you or
some other Apache2 guru on this list might have a suggestion.
Thanks!
Mark
# --
# added for OTRS (http://otrs.org/)
#
# Modified 13 September 2004 with changes from Robert Kehl
# to facilitate browsing to home page.
#
# --
# agent, admin and customer frontend
ScriptAlias /otrs/ "/opt/otrs/bin/cgi-bin/"
Alias /otrs-web/ "/opt/otrs/var/httpd/htdocs/"
# load all otrs modules
Perlrequire /opt/otrs/scripts/apache2-perl-startup.pl
# Apache::Reload - Reload Perl Modules when Changed on Disk
PerlModule Apache::Reload
PerlInitHandler Apache::Reload
# set mod_perl2 options

On Monday, September 13, 2004 2:42 PM
L. Mark Stone
Probably I missed something, so here's the otrs conf file. Perhaps
You did. The trick is to NOT allow ModPerl & Co. become active in /otrs.
See the
you or some other Apache2 guru on this list might have a suggestion.
I have - use this, or transfer to your conf correctly:
# OTRS
Alias otrs "/opt/otrs/bin/cgi-bin/"
Alias otrs-web "/opt/otrs/var/httpd/htdocs/"
<IfModule mod_perl.c>
Perlrequire /opt/otrs/scripts/apache2-perl-startup.pl
</IfModule>
Thanks!
You're always welcome! Robert Kehl -- Mein Rechenschieber ist schon explodiert. Holger Hieronymus zu den Chancen des HSV in der Champions League
participants (2)
-
L. Mark Stone
-
Robert Kehl