On Tue, Mar 12, 2019 at 10:31:39AM +, Jason McIntyre wrote:
> On Tue, Mar 12, 2019 at 01:24:40AM -0500, Alfred Morgan wrote:
> >httpd uses the configuration processor that relayd uses so I was
> >curious to see how this block of sub options were explained in
> >relayd.conf(5) and in
Alfred Morgan(alf...@54.org) on 2019.03.12 01:24:40 -0500:
> httpd uses the configuration processor that relayd uses so I was curious to
> see how this block of sub options were explained in relayd.conf(5) and
Good idea.
But dont draw general conclusions from this please. The parsers are similar
On Tue, Mar 12, 2019 at 01:24:40AM -0500, Alfred Morgan wrote:
>httpd uses the configuration processor that relayd uses so I was
>curious to see how this block of sub options were explained in
>relayd.conf(5) and interestingly enough this is not explained there
>either but there are
Something else that should be considered is to enter a new term
"option_block" into the syntax specification, so instead of this:
connection option
directory option
hsts [option]
[no] log [option]
request option
tcp option
tls option
We now write the syntax as:
connection option|option_block
dir
httpd uses the configuration processor that relayd uses so I was curious to
see how this block of sub options were explained in relayd.conf(5) and
interestingly enough this is not explained there either but there are
examples of the multiple option block being used. One thing I learned from
relayd.
On Mar 11, 2019 5:20 PM, Evan Silberman wrote:
>
> Jason McIntyre wrote:
> > On Mon, Mar 11, 2019 at 12:29:41PM -0700, Evan Silberman wrote:
> > > Jason McIntyre wrote:
> > > >
> > > > Index: httpd.conf.5
> > > > ===
> > > > RCS
Jason McIntyre wrote:
> On Mon, Mar 11, 2019 at 12:29:41PM -0700, Evan Silberman wrote:
> > Jason McIntyre wrote:
> > >
> > > Index: httpd.conf.5
> > > ===
> > > RCS file: /cvs/src/usr.sbin/httpd/httpd.conf.5,v
> > > retrieving revi
On Mon, Mar 11, 2019 at 12:29:41PM -0700, Evan Silberman wrote:
> Jason McIntyre wrote:
> >
> > Index: httpd.conf.5
> > ===
> > RCS file: /cvs/src/usr.sbin/httpd/httpd.conf.5,v
> > retrieving revision 1.103
> > diff -u -r1.103 httpd.
Jason McIntyre wrote:
>
> Index: httpd.conf.5
> ===
> RCS file: /cvs/src/usr.sbin/httpd/httpd.conf.5,v
> retrieving revision 1.103
> diff -u -r1.103 httpd.conf.5
> --- httpd.conf.5 19 Feb 2019 11:37:26 - 1.103
> +++ htt
On Mon, Mar 11, 2019 at 08:59:30AM -0700, Evan Silberman wrote:
>
>
> > On Mar 10, 2019, at 11:55 PM, Jason McIntyre wrote:
> >
> > +Directives which take multiple
> > +.Ar option
> > +values may themselves be grouped in curly brackets.
>
> I think this implies that the directives (which take
> On Mar 10, 2019, at 11:55 PM, Jason McIntyre wrote:
>
> +Directives which take multiple
> +.Ar option
> +values may themselves be grouped in curly brackets.
I think this implies that the directives (which take multiple option values)
may be grouped in curly brackets rather than implying th
On Sun, Mar 10, 2019 at 07:03:36PM -0500, Alfred Morgan wrote:
>jmc wrote on? 2019-03-05 6:58:38:
>> > How does this sound?
>> > A specified option may be written inside curly brackets in order to
>specify
>> > a block of one or more specified options.
>>?
>> regarding y
On Mon, Mar 04, 2019 at 03:46:25PM -0600, Alfred Morgan wrote:
> jmc wrote:
> > i think if you attached a diff to your mail, no matter how poorly
> > written, you would have a better chance of something happening.
>
> How does this sound?
> A specified option may be written inside curly brackets i
jmc wrote:
> i think if you attached a diff to your mail, no matter how poorly
> written, you would have a better chance of something happening.
How does this sound?
A specified option may be written inside curly brackets in order to specify
a block of one or more specified options.
(diff included
On Sun, Mar 03, 2019 at 01:05:54PM -0600, Alfred Morgan wrote:
> There are two formats you can write options in and the man page does not
> mention format 2.
>
> format 1:
> tls key "/etc/ssl/private/server.key"
> tls certificate "/etc/ssl/server.crt"
>
> format 2:
> tls {
> key "/etc/ssl/pri
There are two formats you can write options in and the man page does not
mention format 2.
format 1:
tls key "/etc/ssl/private/server.key"
tls certificate "/etc/ssl/server.crt"
format 2:
tls {
key "/etc/ssl/private/server.key"
certificate "/etc/ssl/server.crt"
}
Besides this, https is pr
16 matches
Mail list logo
