ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
1004
|
Wed Mar 23 11:29:51 2005 |
| Emiliano Gabrielli | AlberT@SuperAlberT.it | Bug report | Linux | r1592 | wrong handling of attachment names | When an attached image name contains a space in its filename and attachment
display is enabled elog builds a wrong url to the image:
http://arcolog.roma2.infn.it:8080/ARCO/050309_170709/peeling+002.jpg
instead of the correct one:
http://arcolog.roma2.infn.it:8080/ARCO/050309_170709_peeling+002.jpg
The more annoing thing is that elogs hangs on this. a strace shows a select
on fd n°3 and 5 that loops forever (returning a timeout error):
send(4, "<141>Mar 23 11:36:25 elogd[22189"..., 35, 0) = 35
rt_sigaction(SIGPIPE, {SIG_IGN}, NULL, 8) = 0
select(1024, [3 5], NULL, NULL, {1, 0}) = 0 (Timeout)
select(1024, [3 5], NULL, NULL, {1, 0}) = 0 (Timeout)
May be the better solution is, after fixing the bug for backward
compatibility with already uploaded images, to implement a forced characters
substitution at upload time, replacing spaces and every character not in a
"allowed chars" list with an underscore |
Draft
|
Thu Oct 21 14:57:14 2021 |
| Chris Körner | chris.koerner@physik.uni-halle.de | Bug report | Linux | 3.14 | wrong server HTTP status code when login failed | Hi,
I am trying to access elog through a python client (https://github.com/paulscherrerinstitute/py_elog) and found a strage strange behavior which may be related server side problem. The python script generates get/post messages via the python requests library. This works fine so far and I can view and post messages. However, if a wrong user/password is provided, the server still returns HTTP status code "200 OK", although login failed. Instead, it should return something like "401 Unauthorized". This behavior later causes problems since the python client thinks login was successful. After experimenting around I think this could be caused by a server side misconfiguration. Any ideas?
I am not sure if this imformation is important: We use LDAP as user/password provider for elog. |
69402
|
Thu Oct 21 15:17:52 2021 |
| Chris Körner | chris.koerner@physik.uni-halle.de | Bug report | Linux | 3.14 | wrong server HTTP status code when login failed | Hi,
I am trying to access elog through a python client (https://github.com/paulscherrerinstitute/py_elog) and found a strage strange behavior which may be related server side problem. The python script generates get/post messages via the python requests library. This works fine so far and I can view and post messages. However, if a wrong user/password is provided, the server still returns HTTP status code "200 OK", although login failed. Instead, it should return something like "401 Unauthorized". This behavior later causes problems since the python client thinks login was successful. After experimenting around I think this could be caused by a server side misconfiguration. Any ideas?
I am not sure if this imformation is important: We use LDAP as user/password provider for elog. |
67232
|
Mon Apr 9 19:58:51 2012 |
| Achim Dreyer | ml10352@adreyer.com | Bug report | All | 2.9.1 | wrong version number in spec file | localhost$ svn diff elog.spec
Index: elog.spec
===================================================================
--- elog.spec (revision 2446)
+++ elog.spec (working copy)
@@ -2,7 +2,7 @@
Name: elog
Summary: elog is a standalone electronic web logbook
-Version: 2.8.1
+Version: 2.9.1
Release: 1
License: GPL
Group: Applications/Networking
|
68872
|
Wed Dec 12 10:44:57 2018 |
| Antonio Iuliano | antonio.iuliano@cern.ch | Question | Linux | 3.1.2 | xmalloc error when filling entries and chaning page | Dear ELOG experts,
the ELOG server on our lab crashes continuosly, when we add a new entry or even if we click the arrows to navigate between entries. Following the FAQ on the website, I have used gdb and found the following error:
xmalloc: not enough memory
[Inferior 1 (process 23271) exited with code 01]
It should be then some allocation issue when we try to access to the entries, but I could not figure the nature of the issue. I was, however, able to reproduce it with a fresh ELOG installation and the same configuration file (ELOG cloned from git and installed today)
Could you please give me any suggestion? I attach here the configuration file we use.
Best regards,
Antonio Iuliano |
|