ELOG Forum

Can I have an RSS feed to a protected log book? Does it also require authentication, or does it bypass it? If it bypasses it, how do I disable RSS?

Thanks,
Chris.

I added this topic to the FAQs at http://midas.psi.ch/elog/faq.html#15

1390

Fri Aug 5 16:17:00 2005

How does RSS interact with password protection?

Can I have an RSS feed to a protected log book? Does it also require authentication, or does it bypass it? If it bypasses it, how do I disable RSS?

Thanks,
Chris.

1388

Fri Aug 5 16:15:04 2005

Re: Top Groups, Show Top Groups, password file and Protect Selection page have nasty interaction

Stefan Ritt wrote:

One note I would like to make however: "Top groups" were invented for having completely separate logbook groups. Before the invention of top groups, one had to run several instances of elogd for different departments for example, where one department should not see the other department's logbooks. But having many departments means having to maintain many elogd daemons. This led to the invention of top groups, so one daemon can serve several independent groups, each having their own [global] section, with probably their own administrator.

In your case however, it would be more applicable not to use top groups, but use nested groups. Like

Group MiniBooNE = Analysis, Miscellaneous
Group Analysis = Charged Current Pi Plus, Neutral Current Coherent Pions
Group Miscellaneous = demo

I presume this is more what you want, and you can avoid some problems which arise from top groups.

The quick attempt I just made to use this doesn't do what I want, which is to require password protection for the Analysis logbook selection page. If you think that *is* possible and I just didn't configure it properly, I'd appreciate pointers. In the meantime though, your bug fixes appear to have solved my top group / password problem and I think I'll proceed with that for now.

Thanks again,
Chris.

1387

Fri Aug 5 14:30:52 2005

Re: "full" only changes color

Stefan Ritt wrote:

Kees Bol wrote:

Stefan, I installed V2.6.0-beta3 and there is a (unwanted) difference. The Text field now appears in the summary-view despite the config specifies:

List Display = ID, Logdate, Author, Book, Chapter, Type, Subject

so in my opinion the text-field should not show up here.

If you do not want text display in the summary view, add

Summary lines = 0

into your config file.

Kees Bol wrote:

Another point: there was some discussion about v2.6.0-beta3 being slow.
I have v2.6.0-beta and v2.6.0-beta3 running side by side on the same server and notice also a big difference in speed, beta3 being much slower.

This is still a mystery to me, since on all machines I try the speed is fine. I'm still waiting for some debugging analysis from users which have this problem. If I cannot reproduce it, I cannot fix it.

After upgrading to v2.6.0-beta4 everything works fine now.
Thanks for your help

1386

Fri Aug 5 12:37:42 2005

Re: Email subject garbaged when set?

Heiko Scheit wrote:

Well not quite. According to the RFC the encoded word must not be longer than 75 characters! Indeed shorter subjects are displayed by pine, but not longer ones as they do not follow RFC2047.
Below is the quote from the RFC.

You are right Big grin

, thanks for this information, I overlooked it.

Now I split a long subject into separate chunks of encoded words, and my pine is happy. Update in CVS.

1385

Fri Aug 5 12:06:47 2005

Re: Top Groups, Show Top Groups, password file and Protect Selection page have nasty interaction

Chris Green wrote:

Index: elogd.c
===================================================================
RCS file: /usr/local/cvsroot/elog/src/elogd.c,v
retrieving revision 1.739
diff -r1.739 elogd.c
21368,21369c21368
< sprintf(str, "?fail=1", user);
< redirect(lbs, str);
---
> redirect(lbs, "?fail=1");

Thanks, applied.

Chris Green wrote:

Regardless (ie if I use the original CVS code or the patched version), a hard-to trace problem occurs with my configuration whereby users are denied access after password entry at the logbook selection page (even when details are verifiably correct), and users are dropped through to the next (non-protected) Top Group page. This problem goes away if "Protect Selection Page" is turned off.

I hope I have fixed this problem, at least it works ok here when I tried with your config file.

One note I would like to make however: "Top groups" were invented for having completely separate logbook groups. Before the invention of top groups, one had to run several instances of elogd for different departments for example, where one department should not see the other department's logbooks. But having many departments means having to maintain many elogd daemons. This led to the invention of top groups, so one daemon can serve several independent groups, each having their own [global] section, with probably their own administrator.

In your case however, it would be more applicable not to use top groups, but use nested groups. Like

Group MiniBooNE = Analysis, Miscellaneous
Group Analysis = Charged Current Pi Plus, Neutral Current Coherent Pions
Group Miscellaneous = demo

I presume this is more what you want, and you can avoid some problems which arise from top groups.

Chris Green wrote:

A kind of "shadow" of this problem occurs if you create a new logbook from the Change Config File page, whereby after creating the new logbook one is dropped through to the next Top Group's selection page after saving the configuration (and the url has ?fail=1 added to it, althoguh line 21368 above is hardly the only place where this could have occurred).

I have not tested this one, but it could well be that the modification I made also fixes this.

1384

Fri Aug 5 11:18:08 2005

Heiko Scheit

h.scheit@mpi-hd.mpg.de

Question

Linux

2.6.0b3

Re: Email subject garbaged when set?

Stefan Ritt wrote:

Chris Green wrote:

The email I get has:

Subject:
=?ISO-8859-1?B?W0Jvb05FLUVMT0ddIE5ldyBzdWJtaXNzaW9uIHRvIENoYXJnZWQgQ3Vyc
mVudCBQaSBQbHVzIGZyb20gQ2hyaXMgR3JlZW4=?=

... which isn't particularly illuminating.

This is the BASE64 encoding of the subject. It was discussed here and I implemented it according to RFC2047.

Well not quite. According to the RFC the encoded word must not be longer than 75 characters! Indeed
shorter subjects are displayed by pine, but not longer ones as they do not follow RFC2047.
Below is the quote from the RFC.

Stefan Ritt wrote:

All subjects I receive look fine in Outlook and Thunderbird, but not under Pine, which apparently does not implement the RFC correctly.

Actually pine implements it correctly but not elogd Smile

The relevant text from the RFC

   An 'encoded-word' may not be more than 75 characters long, including
   'charset', 'encoding', 'encoded-text', and delimiters.  If it is
   desirable to encode more text than will fit in an 'encoded-word' of
   75 characters, multiple 'encoded-word's (separated by CRLF SPACE) may
   be used.

Goto page Previous 1, 2, 3 ... 642, 643, 644 ... 806, 807, 808 Next

ELOG V3.1.5-3fb85fa6