> On 3 Aug 2017, at 08:30, Jim Jagielski wrote:
>
> It's just GUI magic... Basically, it will internally take '1.1' and
> convert it to 11, 1.0 to 10, etc...
If that's the case, I would recommend going 2 decimal places (1.1 = 100, 1.25 =
125, etc.) to allow using percentages.
If I extrapolate on the idea of what Nick is saying, it sounds like it could be
a proposal to simply define these SSL policies in a macro. Personally, I prefer
that approach over adding another set of directives (but it's a preference, not
an opposition). The downside is that mod_macro would
On Fri, Aug 4, 2017 at 4:26 AM, Stefan Eissing
wrote:
> I talked about some kind of SSL Policy definition in httpd's configuration
> in the past and am now about to get serious about it. Here is what I wan to
> do:
>
> Recap: the general idea is
> 2. Provide a set of
On 08/04/2017 04:38 AM, Luca Toscano wrote:
I agree that mod_macro is flexible enough to improve the reusability of
httpd's configuration, but I don't think that the goals that Stefan has
in mind are satisfiable with your proposed solution.
If we find ourselves doing more of this syntactic
Hi Nick,
2017-08-04 13:06 GMT+02:00 Nick Gearls :
> This can be done using mod_macro without any additional code
my 2c: Stefan's point is to simplify the management of things that have
been done up to now using workarounds and elegant hacks:
> On 04-08-2017 11:26,
This can be done using mod_macro without any additional code
On 04-08-2017 11:26, Stefan Eissing wrote:
I talked about some kind of SSL Policy definition in httpd's configuration
in the past and am now about to get serious about it. Here is what I wan to
do:
Recap: the general idea is
1. Give
I talked about some kind of SSL Policy definition in httpd's configuration
in the past and am now about to get serious about it. Here is what I wan to
do:
Recap: the general idea is
1. Give a set of SSL directives a name and allow the user to apply that name
in several virtual hosts.
2.