On 12 December 2017 at 11:32, Stefan Eissing
wrote:
> Fellow Apache developers: if we want to make an X-mas 2.4 release for the
> people on this planet, the backports in STATUS need your attention:
>
> B2: mod_remoteip: Add PROXY protocol support
> - needs 1 more vote!
>
> I find that trying to
On Tue, Dec 12, 2017 at 3:32 AM, Stefan Eissing
wrote:
> Fellow Apache developers: if we want to make an X-mas 2.4 release for the
> people on this planet, the backports in STATUS need your attention:
>
> B2: mod_remoteip: Add PROXY protocol support
> - needs 1 more vote!
The caveat to this one
Help !
Your reaction makes me very sad that you accuse me.
Other dev’s are slilence about mod_md, as you said before: they are shoulder
clapping etc. And you said: You got to be kiddding me! Afterwords maybe better
that I was also more silent. But on the other-hand we did not discovered all
th
There is so much personal offence and mal-attribution in this mail, I am not
sure where you get that from. I ask you to take a deep breath and consider what
you want here. Just because I do what I feel is right does not make me your
enemy. Give me a break.
-Stefan
> Am 12.12.2017 um 16:19 sch
- No, I will not change the endless retry behaviour.
I still not see the reason for retries on all the errors, I am not
aware of other modules doing it this way.
But Ok, when mdnotifycmd on error is added (see other post feature
request). Then I vote a SUPER +1 for an experimental relea
On errors with sigining up and renewing there are only log entries,
and mod-md is retrying in a loop.
Now the MDNotifyCmd is only triggered when it is ok, seems logical
also notify when there is some wrong.
Request :
Use MDNotifyCmd for the first error AH10057 and it should be nice with
t
> Am 12.12.2017 um 14:37 schrieb Steffen :
>
> The curl error was just to show you the debug log entries which you asked.
>
> This curl error we discussed by mail already in the very beginning (mod_md
> does not work with curl openssl on Windows).
>
> 1.1.0 is working fine so far.
>
> I am
The curl error was just to show you the debug log entries which you
asked.
This curl error we discussed by mail already in the very beginning
(mod_md does not work with curl openssl on Windows).
1.1.0 is working fine so far.
I am only testing rare cases (you asked to test).
Steffen
O
*without* introducing new ones, I meant. Please provide a log.
> Am 12.12.2017 um 14:21 schrieb Stefan Eissing :
>
>
>
>> Am 12.12.2017 um 14:17 schrieb Steffen :
>>
>> To be clear : As I said the curl error I have introduced (by my self), so I
>> know exactly what is wrong.
>
> Ah, that wa
> Am 12.12.2017 um 14:17 schrieb Steffen :
>
> To be clear : As I said the curl error I have introduced (by my self), so I
> know exactly what is wrong.
Ah, that was not clear to me.
So, what is the error happening with you introducing new ones? Is there nothing
to see in the logs or did I
To be clear : As I said the curl error I have introduced (by my
self), so I know exactly what is wrong.
Your reply shows me that you want to keep the endless retry loop. I
the worst case a user can end with a non working SSL because a
certificate is not renewed.
Why is it retried again an
And btw. what is the Windows OS version that your server runs on?
And since you had mod_md running before, what did change in relation to
Windows and the curl you use?
> Am 12.12.2017 um 13:58 schrieb Stefan Eissing :
>
>
>
>> Am 12.12.2017 um 13:47 schrieb Steffen :
>>
>> It was happening be
> Am 12.12.2017 um 13:47 schrieb Steffen :
>
> It was happening before 1.1.0, but i did not give it attention, seen it in
> several situations which all I unfortunate cannot recall (see the retries as
> example https://github.com/icing/mod_md/issues/52and
> https://github.com/icing/mod_md/is
It was happening before 1.1.0, but i did not give it attention, seen
it in several situations which all I unfortunate cannot recall (see
the retries as example https://github.com/icing/mod_md/issues/52 and
https://github.com/icing/mod_md/issues/62 ).
It is a more serious issue then I though
Sorry, Rüdiger.
> Am 12.12.2017 um 10:36 schrieb rj...@apache.org:
>
> Author: rjung
> Revision: 1817894
> Modified property: svn:log
>
> Modified: svn:log at Tue Dec 12 09:36:05 2017
> --
> --- svn:log (original)
> +++
Fellow Apache developers: if we want to make an X-mas 2.4 release for the
people on this planet, the backports in STATUS need your attention:
B1: mod_proxy, mod_ssl: Handle SSLProxy* directives in sections,
- needs 1 more vote!
B2: mod_remoteip: Add PROXY protocol support
- needs 1 more vote
Can you switch to "LogLevel md:debug" for a while and send me the details? Did
this start on the v1.1.0 or before that?
> Am 11.12.2017 um 16:09 schrieb Steffen :
>
>
> Running 1.1.0 with the new naming.
>
> When mod_md encounters an error it looks like it is going in a endless loop:
>
>
> [
Right, you are. Fixed in r1817894.
Changes and Lookups happen now in the same main config pool, so the logic for
subpools is no longer needed.
Thanks for reviewing!
-Stefan
> Am 11.12.2017 um 21:08 schrieb Ruediger Pluem :
>
>
>
> On 12/07/2017 04:11 PM, ic...@apache.org wrote:
>> Author: i
18 matches
Mail list logo