Forum .LRN Q&A: Re: Redirecting problem

Collapse
17: Re: Redirecting problem (response to 1)
Posted by Zakaria Saja on
I finally able to install dotlrn using your debian package.

First I must edit /etc/init.d/dotlrn from the line:

DAEMON=/usr/sbin/aolserver4-nsd
to:
DAEMON=/usr/sbin/nsd

Then I try to run it again: /etc/init.d/dotlrn start

I point my browser to http://localhost:8000 and I get installation page. I filled it then proceed to installation. It creates the database and said it restart the dotlrn. So I do /etc/init.d/dotlrn start again.

But when I point my browser to http://localhost:8000 I get error. After trying with lynx I find out that:

  1. It send a cookie ad_s which I allow
  2. then redirect to http://localhost:8000/dotlrn/index
  3. then redirect to http://localhost:8000/register/?return%5furl=http%3a%2f%2flocalhost%3a8000%2fdotlrn%2findex
  4. then redirect to https://localhost:8000:8443/register/?return%5furl=http%3a%2f%2flocalhost%3a8000%2fdotlrn%2findex

There must be something very wrong because it try to redirect to localhost:8000:8443

Here my system details

Linux zakbox 2.6.6-1-686 #1 Wed May 12 14:57:57 EST 2004 i686 GNU/Linux
Debian Sarge/Testing
dotlrn                 2.0.3-2
aolserver4             4.0.5-1
aolserver4-doc         4.0.5-1
aolserver4-nscache     1.5-1
aolserver4-nsldap      0.0.r8-1
aolserver4-nsopenssl   3.0beta12-2
aolserver4-nspostgres  4.0-1
aolserver4-nssha1      0.1-1
postgresql             7.4.2-4

Currently I'm able to workaround the problem by commenting line ns_param nsopenssl from /etc/aolserver4/dotlrn.tcl. Is there more permanent fix, so I could use SSL?

Collapse
18: Re: Redirecting problem (response to 17)
Posted by Jade Rubick on
Zakaria, this is a problem I just fixed on OpenACS. I'm sure it hasn't been reflected in the dotlrn package yet.

Here's the post where I reported the same problem:
https://openacs.org/forums/message-view?message_id=194108

The fixes are in CVS. You can browse CVS via http://cvs.openacs.org

You will not have this problem is you change your installation to use the standard ports of 80 and 443. So you can either change the ports, or change your local installation with these fixes. Or you can wait until the package itself it updated.