| ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
|
1690
|
Tue Feb 14 14:23:04 2006 |
 | Dimitrios Tsirigkas | dimitrios.tsirigkas@cern.ch | Question | Linux | 2.6.1 | Re: Accessing elog through two apache servers... | Hi Stefan,
| Stefan Ritt wrote: |
Hi Dimitrios,
I know where your problem is and you could actually help me in solving it. The reason of the problem is the redirection. After you login, you get redirected (via the HTTP "Location:" statement) to the start page. In an very old version of ELOG, I had relative redirection. So from https://cmsdaq.cern.ch/elog/DAQ/?cmd=Login I did a redirect to "." and voila I the browser asked for https://cmsdaq.cern.ch/elog/DAQ/.
|
But my problem begins before I log in. Trying to load https://cmsdaq.cern.ch/elog/DAQ/?cmd=Login will get me in the infinite redirection directly. Besides, I do have URL = https://cmsdaq.cern.ch/elog/ in my configuration file, so the redirection should work in my case (since I'm trying to access it through cmsdaq) and fail in every other case. Is that right or is there something I'm missing?
Cheers,
Dimitris |
|
1691
|
Tue Feb 14 16:06:28 2006 |
| Dimitrios Tsirigkas | dimitrios.tsirigkas@cern.ch | Question | Linux | 2.6.1 | Re: Accessing elog through two apache servers... | Hi,
The problem was coming from the fact that elog did not supports request coming from multiple hops through proxies. You got the ful string of them in the X-Forwarded-host header. Hence, you have to pick only the first one, terminated by a ','.
Here's the patch:
--- elogd-orig.c 2006-02-14 15:47:51.000000000 +0100
+++ elogd.c 2006-02-14 15:49:42.000000000 +0100
@@ -20985,6 +20985,8 @@
strcpy(str2, http_host);
if (strchr(str2, ':'))
*strchr(str2, ':') = 0;
+ if (strchr(str2, ','))
+ *strchr(str2, ',') = 0;
if (!strieq(str, str2)) {
redirect(lbs, _cmdline);
return FALSE;
Cheers
Eric and Dimitris |
|
1695
|
Wed Feb 15 18:13:25 2006 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Linux | 2.6.1 | Re: Accessing elog through two apache servers... | | Thanks for the patch, I committed it to Subversion Revision #1657. |
|
1610
|
Thu Jan 19 15:23:02 2006 |
| Stefan Ritt | stefan.ritt@psi.ch | Bug report | | 2.6.1 | Re: Access to global configuration in v2.6.1 | > I just installed v.2.6.1 coming from the previous 2.6.0 (on Win2000)
> When I access the "configuration" function from a logbook, in the cfg page I only see two buttons in the header
> (save or cancel); in the previous version I saw more buttons there ("global config", "create new logbook" and so
> on), so here I'm unable to access global configuration or logbook management (except for current logbook options).
I tried to reproduce your problem, but could not. In my windows installation it looks fine. You only see the
(save and cancel) buttons only if you go to "Change [global]", otherwise you see the "Change [global]", "Delete
this logbook" etc. buttons. Have you tried with the default elogd.cfg which comes from the distribution? |
|
1616
|
Sat Jan 21 14:02:57 2006 |
| Giorgio Croci Candiani | g.crocic@libero.it | Bug report | | 2.6.1 | Re: Access to global configuration in v2.6.1 |
> I tried to reproduce your problem, but could not. In my windows installation it looks fine. You only see the
> (save and cancel) buttons only if you go to "Change [global]", otherwise you see the "Change [global]", "Delete
> this logbook" etc. buttons. Have you tried with the default elogd.cfg which comes from the distribution?
Yes, I tried that. Maybe I'll have some other try on other PCs and investigate further, I'll surely let you know. Thanks
for the prompt response and compliments for your very good work! ELog is really a great piece of software. |
|
1626
|
Wed Jan 25 01:08:06 2006 |
| Giorgio Croci Candiani | g.crocic@libero.it | Bug report | | 2.6.1 | Re: Access to global configuration in v2.6.1 | > > I just installed v.2.6.1 coming from the previous 2.6.0 (on Win2000)
> > When I access the "configuration" function from a logbook, in the cfg page I only see two buttons in the header
> > (save or cancel); in the previous version I saw more buttons there ("global config", "create new logbook" and so
> > on), so here I'm unable to access global configuration or logbook management (except for current logbook options).
>
> I tried to reproduce your problem, but could not. In my windows installation it looks fine. You only see the
> (save and cancel) buttons only if you go to "Change [global]", otherwise you see the "Change [global]", "Delete
> this logbook" etc. buttons. Have you tried with the default elogd.cfg which comes from the distribution?
Here I am again... I built and installed v2.6.1 also on a different system, this time on linux; i tried both with the
existing cfg file and with the new cfg.
Choosing "configuration", I still only see the current logbook configuration file section with "Save" and "cancel"
buttons, no access to global config whatsoever; the same as I saw on windows version. I tried version 2.6.1-1622.
Regards
Giorgio |
|
1627
|
Wed Jan 25 08:24:28 2006 |
| Stefan Ritt | stefan.ritt@psi.ch | Bug report | | 2.6.1 | Re: Access to global configuration in v2.6.1 | > Here I am again... I built and installed v2.6.1 also on a different system, this time on linux; i tried both
with the
> existing cfg file and with the new cfg.
> Choosing "configuration", I still only see the current logbook configuration file section with "Save" and "cancel"
> buttons, no access to global config whatsoever; the same as I saw on windows version. I tried version 2.6.1-1622.
I tried again, using the configuration file from the distribution (elog:1627/1). Hitting "config", I see the picture
attached (elog:1627/2). So it's a mystery why it is different in your case... |
|
1628
|
Wed Jan 25 12:08:13 2006 |
| Giorgio Croci Candiani | g.crocic@libero.it | Bug report | | 2.6.1 | Re: Access to global configuration in v2.6.1 | > I tried again, using the configuration file from the distribution (elog:1627/1). Hitting "config", I see the picture
> attached (elog:1627/2). So it's a mystery why it is different in your case...
Indeed... I peeked into the code, and I got the feeling it could be a matter of incorrect user setup (though I have no
users/authorizations defined at all) or maybe browser cookies. A thin trail, but I'll try some debug directly on the
code and, should I come up with something, I'll surely notice you.
Thanks for your support! |
|