Thanks William for your valuable response. It helped a lot in understanding
httpd parsing.
Really appreciate your time and knowledge.
With Regards,
Venkatesh
On Thu, Sep 6, 2018 at 8:31 PM, William A Rowe Jr
wrote:
> On Wed, Sep 5, 2018 at 10:11 PM, alchemist vk
> wrote:
>
>> Hi William,
>>
On Wed, Sep 5, 2018 at 10:11 PM, alchemist vk
wrote:
> Hi William,
> Sorry for late response.. I appreciate your response.
> Small clarification: You meant to say, with space as delimiter, httpd
> parses will consider space separated tokens as each individual httpd
> directives?
>
The synt
Hi William,
Sorry for late response.. I appreciate your response.
Small clarification: You meant to say, with space as delimiter, httpd
parses will consider space separated tokens as each individual httpd
directives?
With Regards,
Venkatesh
On Mon, Aug 27, 2018 at 7:03 PM, William A Rowe Jr
A good argument for following httpd documented convention.
If you want to continue exploring, you would want to quote the cipher
string, since httpd would take apart unquotes, space separated tokens as
different httpd directive arguments, and you surely don't want that.
On Sat, Aug 25, 2018, 20:0
Hi All,
openssl standard says " The cipher list consists of one or more *cipher
strings* separated by colons. Commas or spaces are also acceptable
separators but colons are normally used". But apache says "directive uses
a *colon-separated* *cipher-spec* string consisting of OpenSSL cipher
spec
