ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
69790
|
Thu Apr 25 02:11:08 2024 |
| Konstantin Olchanski | olchansk@triumf.ca | Question | Linux | Other | 3.1.5 | Re: Imagemagick not working on Ubuntu |
Please see https://daq00.triumf.ca/DaqWiki/index.php/Ubuntu#Enable_elog_PDF_preview
see https://stackoverflow.com/questions/52998331/imagemagick-security-policy-pdf-blocking-conversion
xemacs -nw /etc/ImageMagick-6/policy.xml
remove this section at the end:
<!-- disable ghostscript format types -->
<policy domain="coder" rights="none" pattern="PS" />
<policy domain="coder" rights="none" pattern="PS2" />
<policy domain="coder" rights="none" pattern="PS3" />
<policy domain="coder" rights="none" pattern="EPS" />
<policy domain="coder" rights="none" pattern="PDF" />
<policy domain="coder" rights="none" pattern="XPS" />
K.O. |
69807
|
Mon Jul 22 16:17:55 2024 |
| André | andre.althaus@tu-dortmund.de | Bug report | All | 3.1.5 | HTTP headers should be parsed case insensitive |
I'm trying to run elog behind haproxy, but get the error "Invalid Content-Length in header" on posting.
As stated in the manual, haproxy rewrites all headers to lower case.
elogd parses the content-length header case sensitive which is against the HTTP RFC. This might also apply to other headers that get parsed.
For now I'm using the workaround from the manual:
global
h1-case-adjust content-length Content-Length
h1-case-adjust content-type Content-Type
backend elog
option h1-case-adjust-bogus-server
server elog 127.0.0.1:8080
But as the manual states, this should not be used as a permanent solution. |
69817
|
Wed Jul 31 14:21:21 2024 |
| Stefan Ritt | I cstefan.ritt@psi.ch | Bug report | All | 3.1.5 | Re: HTTP headers should be parsed case insensitive |
I changed elog to interprete the content-length header case in-sensitive and committed the change. Can you try again?
Stefan
André wrote: |
I'm trying to run elog behind haproxy, but get the error "Invalid Content-Length in header" on posting.
As stated in the manual, haproxy rewrites all headers to lower case.
elogd parses the content-length header case sensitive which is against the HTTP RFC. This might also apply to other headers that get parsed.
For now I'm using the workaround from the manual:
global
h1-case-adjust content-length Content-Length
h1-case-adjust content-type Content-Type
backend elog
option h1-case-adjust-bogus-server
server elog 127.0.0.1:8080
But as the manual states, this should not be used as a permanent solution.
|
|
69819
|
Mon Aug 5 20:45:15 2024 |
| Truupe | pijuels@gmail.com | Question | Other | 3.1.5 | Elog on FreeBSD |
Anyone using elog on FreeBSD nowadays? I know it used to be in the ports tree about 10 years ago but seems to be abandoned. Tried to compile from source on 14.1, but no luck there. |
69820
|
Mon Aug 5 21:15:08 2024 |
| Truupe | pijuels@gmail.com | Question | Other | 3.1.5 | Re: Elog on FreeBSD |
Welp, nevermind, I dug a little more and managed to compile it on 14.1 using cmake.
Truupe wrote: |
Anyone using elog on FreeBSD nowadays? I know it used to be in the ports tree about 10 years ago but seems to be abandoned. Tried to compile from source on 14.1, but no luck there.
|
|
69843
|
Fri Dec 6 09:39:44 2024 |
| Olivier MARTIN | amande.olive@yahoo.fr | Question | Linux | 3.1.5 | Probleme TLS |
Hello,
I would like to notify by email as soon as an entry is created or modified.
I declared my SMTP which uses TLS security.
The following error message appears : Erreur d'envoi de mail via "smtp.xxxx.xxx.xxx.fr": 5.7.0 Must issue a STARTTLS command first
Is there a solution ?
|
69845
|
Fri Dec 6 10:59:52 2024 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Linux | 3.1.5 | Re: Probleme TLS |
TSL is not implemented in ELOG. Maybe I find time some day to do that, but if we have any volunteers in our community who could help me with that I would appreciate.
Stefan
Olivier MARTIN wrote: |
Hello,
I would like to notify by email as soon as an entry is created or modified.
I declared my SMTP which uses TLS security.
The following error message appears : Erreur d'envoi de mail via "smtp.xxxx.xxx.xxx.fr": 5.7.0 Must issue a STARTTLS command first
Is there a solution ?
|
|
69848
|
Mon Dec 9 10:23:32 2024 |
| Olivier MARTIN | amande.olive@yahoo.fr | Question | Linux | 3.1.5 | Re: Probleme TLS |
Thanks,
Does email notification from a Gmail address work? It is noted that port 465 must be used for SSL use? Is this correct :
SMTP host : smtp.gmail.com
SMTP port = 465
SMTP username = monadresse@gmail.com
And, should I enter the password attached to my Gmail email and where?
Thanks in advance.
Stefan Ritt wrote: |
TSL is not implemented in ELOG. Maybe I find time some day to do that, but if we have any volunteers in our community who could help me with that I would appreciate.
Stefan
Olivier MARTIN wrote: |
Hello,
I would like to notify by email as soon as an entry is created or modified.
I declared my SMTP which uses TLS security.
The following error message appears : Erreur d'envoi de mail via "smtp.xxxx.xxx.xxx.fr": 5.7.0 Must issue a STARTTLS command first
Is there a solution ?
|
|
|