AuthModule::HTTPBasicAuth::Replace
This # In case there is a leading domain in the REMOTE_USER, you can # replace it by the next config option. # $Self->{'AuthModule::HTTPBasicAuth::Replace'} = 'example_domain\\'; (and Customer::AuthModule::HTTPBasicAuth::Replace) would be useful to me if there weren't the constraint that 'Replace' has to occur at the beginning of REMOTE_USER. My REMOTE_USER has the form user@domain, so I must continue to modify the code to get it reduced to plain 'user'. If the anchoring were removed, in order to allow the pattern to be deleted to occur anywhere in the string, I doubt if anyone already using the feature would be affected. Could it be done? Jim
hi, my company is in charge of the administration of a heavily used otrs installation. There are about 30 concurrent users and 260 tickets per day. The analysis of the file /var/log/apache2/error.log over a period of 3 days shows many entries like: :Apache IO flush: (103) Software caused connection abort at -e line 0:Apache IO flush: (104) Connection reset by peer at -e line 0:Apache IO flush ... there are 373 entries altogether 18: :Apache IO flush: (104) Connection reset by peer at -e line 0 355: :Apache IO flush: (103) Software caused connection abort at -e line 0 These entries worry me. What do they mean? Do i have to change something or can i ignore it? details of the otrs installation: otrs 2.04 os: linux debian sarge amd64 relevant debian packages and versions: apache2 2.0.5.4-5sarge1 apache-mpm-prefork libapache2-mod-perl2 1.999.21-1 libapache-dbi-perl 0.94-2 mysql-server-4.1 4.1.11a-4sarge Regards Martin Leja
participants (2)
-
Jim Wight -
Martin Leja