Re: https:// changed to http:// when submit button is clicked, posted by Stefan Ritt on Fri Mar 7 09:39:45 2003
|
> > I'm using elog 2.3.1 on redhat 7.1 and using stunnel to redirect from port
> > 443 to 8080. When I try to add a new record (click submit) https:// in the
> > browser gets changed to http://. I ve tried three browsers all with the
same
> > result. If I go into the address field and change it to https:// after
> > getting a 404 error it works. The record gets posted.
This is due to a change we had to do in the redirection of the pages. If you
submit a page, the result is a redirection using the HTTP
statement "Location: ..." inside the header. While this was a relative link
in the previous versions, we changed this into an absolute link, which then
agrees with the standard. But since elgod does not know if it runs
under "http:" or "https:", you have now to add the line
URL = https://your.server:port
into elogd.cfg. I will add this note into the documentation.
- Stefan |
|
Re: https:// changed to http:// when submit button is clicked, posted by Robert Keeney on Fri Mar 7 12:32:34 2003
|
Operator error. Figures!
Elog has worked fine for a log time then I upgraded and added stunnel at the
same time. A case of not seeing the forest for the trees.
Thanks for the help.
> > > I'm using elog 2.3.1 on redhat 7.1 and using stunnel to redirect from port
> > > 443 to 8080. When I try to add a new record (click submit) https:// in the
> > > browser gets changed to http://. I ve tried three browsers all with the
> same
> > > result. If I go into the address field and change it to https:// after
> > > getting a 404 error it works. The record gets posted.
>
> This is due to a change we had to do in the redirection of the pages. If you
> submit a page, the result is a redirection using the HTTP
> statement "Location: ..." inside the header. While this was a relative link
> in the previous versions, we changed this into an absolute link, which then
> agrees with the standard. But since elgod does not know if it runs
> under "http:" or "https:", you have now to add the line
>
> URL = https://your.server:port
>
> into elogd.cfg. I will add this note into the documentation.
>
> - Stefan |
Problems with 2.3.2, posted by nick on Thu Mar 13 17:30:16 2003
|
Ive just installed the RPM of Elog 2.3.2 and ive found a bug relating to
port bindings, basically im running elog bound to port 81 and when i
install the new RPM it refuses to bind to this port, i tried port 8080 and
that worked fine
Any ideas ? |
|
Re: Problems with 2.3.2, posted by Stefan Ritt on Thu Mar 13 17:33:58 2003
|
> Ive just installed the RPM of Elog 2.3.2 and ive found a bug relating to
> port bindings, basically im running elog bound to port 81 and when i
> install the new RPM it refuses to bind to this port, i tried port 8080 and
> that worked fine
>
> Any ideas ?
This is a bug I discovered myself just today, so we are working on it. I
expect this to be fixed by tomorrow or somewhen during this weekend.
- Stefan |
|
Re: Problems with 2.3.2, posted by Stefan Ritt on Fri Mar 14 10:30:25 2003
|
> > Ive just installed the RPM of Elog 2.3.2 and ive found a bug relating to
> > port bindings, basically im running elog bound to port 81 and when i
> > install the new RPM it refuses to bind to this port, i tried port 8080
and
> > that worked fine
The bug has been fixed in V 2.3.3 which has been released today. |
|
Re: Elog 2.3.3, problems of 2.3.2 solved, posted by djek on Thu Mar 20 21:07:09 2003
|
> > After upgrading from 2.3.1 to 2.3.3, elog is not able to load any resources
> > as stylesheets, images or passwordfiles.
> >
> > Cannot open file /usr/local/elogdata/logbooks/djeks/password!
>
> If you installed from the RPM, elogd runs under the user "elog". If you have
> installed a previous version under a different user, it might be that elogd
> does not have read or write access to it. A
>
> "chown -R elog.elog /usr/local/elogdata"
>
> might help.
>
It did, a lot, guess I missed that one in the changelog.
Had some trouble with subdir too:
changed it to its full path
restarted elogd
worked
As a test I changed subdir to it's relative path
restarted
It kept working
mmmm, I wonder where that twighlight tune comes from ... |
|
Re: Elog 2.3.3, problems of 2.3.2 only partly solved, posted by Stefan Ritt on Thu Mar 20 21:07:09 2003
|
> After upgrading from 2.3.1 to 2.3.3, elog is not able to load any resources
> as stylesheets, images or passwordfiles.
>
> Cannot open file /usr/local/elogdata/logbooks/djeks/password!
If you installed from the RPM, elogd runs under the user "elog". If you have
installed a previous version under a different user, it might be that elogd
does not have read or write access to it. A
"chown -R elog.elog /usr/local/elogdata"
might help.
- Stefan |
Elog 2.3.3, problems of 2.3.2 only partly solved, posted by djek on Thu Mar 20 21:07:09 2003
|
After upgrading from 2.3.1 to 2.3.3, elog is not able to load any resources
as stylesheets, images or passwordfiles.
Cannot open file /usr/local/elogdata/logbooks/djeks/password!
oops? |