You proberly set up your aliases correctly but you have to make sure that your ServerName is set up correctly as well. That is to say, if somebody tries to go to http://moodle.truman.edu/moodle Apache tries to fix that by adding the trailing slash. Apache does that by reconstructing the URL using the ServerName directive in the httpd.conf. If that is not set correctly you often run into the trouble of being redirect values such as 127.0.0.1 or localhost.
Hope that helps, alex Chad Mohler wrote: >Hi, all. > > I'm a little new to configuring web servers, so I hope one of >you might be able to help me out here. I'm the administrator of >Truman's Moodle course management system (an open-source alternative >to Blackboard, running on a Debian box), and I'm trying to correct an >error that pops up occasionally when people log in to the Moodle >site. As far as I can tell, here is when the error occurs... >when people login to Moodle from http://moodle.truman.edu rather than >from the explicit URL of the particular Moodle course page they >intend to go to, and... >when (after all login info is entered and the user hits the login >button) the browser pauses even momentarily (for instance, to ask >whether it should save the entered password) before the next page is >loaded. >Under those conditions, I think what happens is that the Moodle login >script re-directs the user to http://moodle.truman.edu/moodle . >Going to that address (via login script or not), however, results in >the error message "The connection was refused when attempting to >contact 127.0.0.1." Adding a backslash to the end of that address >(i.e., changing it to http://moodle.truman.edu/moodle/ ) results in >direction to the right page. Unfortunately, no matter how much I >edit the Moodle config file to indicate that Moodle should direct >users to http://moodle.truman.edu/moodle/ , I think it's directing >users from the login page to http://moodle.truman.edu/moodle , >resulting in the error. > > I thought I could work around that problem by putting an alias >in the /etc/apache/httpd.conf file of the following form: > >>Alias /moodle /usr/share/moodle/ >> >><DirectoryMatch /usr/share/moodle/> >> >>Options +FollowSymLinks >>AllowOverride None >> >>order deny,allow >># deny from all >># allow from 127.0.0.0/255.0.0.0 >> allow from all >> >><IfModule mod_php4.c> >> php_flag magic_quotes_gpc On >> php_flag magic_quotes_runtime Off >> php_flag file_uploads On >> php_flag short_open_tag On >> php_flag session.auto_start Off >> php_flag session.bug_compat_warn Off >> >> php_value upload_max_filesize 2M >> php_value post_max_size 2M >></IfModule> >> >></DirectoryMatch> > > I then restarted the apache server using "apachectl graceful," >but unfortunately, I still get the "refuse to connect to 127.0.0.1" >error when I go to http://moodle.truman.edu/moodle . Does anyone >have any suggestions on what to do to get that address to load >correctly (i.e., to get it to load the same page that loads with the >backslashed version of that address, http://moodle.truman.edu/moodle/ >)? Thanks for the help. > >--- Chad Mohler > > >-- >This message has been 'sanitized'. This means that potentially >dangerous content has been rewritten or removed. The following >log describes which actions were taken. > >Sanitizer (start="1107193916"): > Part (pos="1319"): > ParseHeader (): > Ignored junk while parsing header: > > SanitizeFile (filename="unnamed.txt", mimetype="text/plain"): > Match (names="unnamed.txt", rule="2"): > Enforced policy: accept > > >Anomy 0.0.0 : Sanitizer.pm >$Id: Sanitizer.pm,v 1.79 2003/06/19 19:22:00 bre Exp $ > ----------------------------------------------------------------- To get off this list, send email to [EMAIL PROTECTED] with Subject: unsubscribe -----------------------------------------------------------------
