Am 05.09.2015 um 19:32 schrieb Seyyed Hesamoddin Ghasemi:
How can force Apache server to use a constant value sequence number in
all the sessions? Is this possible?
I'm an Msc computer engineering student and I need to do this in one of
the steps of my thesis implementations.
I would be happy to
Hi,
How can force Apache server to use a constant value sequence number in all
the sessions? Is this possible?
I'm an Msc computer engineering student and I need to do this in one of the
steps of my thesis implementations.
I would be happy to hear your response.
Ideally, the patch would be broken up into separate ones; for example,
the change for maintainer-mode should be sep from the fixes of warnings,
etc.
> On Sep 4, 2015, at 9:26 AM, Stefan Eissing
> wrote:
>
>
On 05 Sep 2015, at 9:21 AM, Stefan Eissing wrote:
> yes, it should. where do you not see it?
>
> (i wish we'd use branches instead of this patch file madness)
A branch is possible, create one beneath here:
http://svn.apache.org/repos/asf/httpd/httpd/branches/
Regards,
Graham
—
On Sat, Sep 5, 2015 at 3:21 AM, Stefan Eissing
wrote:
> (i wish we'd use branches instead of this patch file madness)
I think a short-lived feature branch would be acceptable. I'm
personally a pretty primitive svn user.
On 09/04/2015 10:59 AM, Kaspar Brand wrote:
On 02.09.2015 01:54, Jeff Trawick wrote:
On 08/30/2015 02:30 AM, Kaspar Brand wrote:
today's situation, because this assessment misses the fact that with the
current RFC-6066-based implementation, stapling can't fully achieve the
goal of obviating OCS
On 5 Sep 2015, at 11:53, Ben Laurie wrote:
> On Sat, 5 Sep 2015 at 09:32 Kaspar Brand wrote:
>> On 04.09.2015 17:54, Rob Stradling wrote:
>>> Today, roughly 25% of HTTPS servers on the Internet have OCSP stapling
>>> enabled. Browsers aren't likely to start hard-failing by default until
>>> th
On Sat, 5 Sep 2015 at 09:32 Kaspar Brand wrote:
> On 04.09.2015 17:54, Rob Stradling wrote:
> > Today, roughly 25% of HTTPS servers on the Internet have OCSP stapling
> > enabled. Browsers aren't likely to start hard-failing by default until
> > that % is a lot higher.
> >
> > The vast majority
On 04.09.2015 17:54, Rob Stradling wrote:
> Today, roughly 25% of HTTPS servers on the Internet have OCSP stapling
> enabled. Browsers aren't likely to start hard-failing by default until
> that % is a lot higher.
>
> The vast majority of the servers that have OCSP stapling enabled are
> running
In core-h2-all-in-one-v4.patch line 8586
+if (!offers || ap_array_contains(offers, *protos)) {
the old ap_array_contains is in use
On 9/5/2015 12:21 AM, Stefan Eissing wrote:
yes, it should. where do you not see it?
(i wish we'd use branches instead of this patch file madness)
Am 05.0
yes, it should. where do you not see it?
(i wish we'd use branches instead of this patch file madness)
> Am 05.09.2015 um 06:12 schrieb Gregg Smith :
>
> Shouldn't this be ap_array_str_contains now in h2_switch.c?
>
> +while (*protos) {
> +/* Add all protocols we know (tls or clear)
11 matches
Mail list logo