So, I was looking at all the system calls we make in a single request,
and comparing it to nginx.
We were actually pretty close, baring supporting our features like
htaccess, there was only one thing that stood out.
Glibc is opening, calling fstat twice, and then reading /etc/localtime
for every
@@
-*- coding: utf-8
-*-
Changes with Apache 2.3.16
+ *) mod_ssl: Add support for RFC 5077 TLS Session tickets.
+ [Paul Querna]
This is somewhat misleading, I think. Session tickets are supported in
mod_ssl as soon as you compile it against OpenSSL 0.9.8f or later (they
default
On Tue, Nov 15, 2011 at 9:25 AM, Rüdiger Plüm
ruediger.pl...@vodafone.com wrote:
Original-Nachricht
Betreff: svn commit: r1202257 - in /httpd/httpd/trunk/server/mpm/event:
config3.m4 equeue.c equeue.h event.c
Datum: Tue, 15 Nov 2011 15:51:04 GMT
Von: pque...@apache.org
On Tue, Nov 15, 2011 at 9:17 AM, Stefan Fritsch s...@sfritsch.de wrote:
On Tue, 15 Nov 2011, pque...@apache.org wrote:
Author: pquerna
Date: Tue Nov 15 15:49:19 2011
New Revision: 1202255
URL: http://svn.apache.org/viewvc?rev=1202255view=rev
Log:
disable mod_reqtimeout if not configured
On Wed, Nov 16, 2011 at 1:20 AM, Rüdiger Plüm
ruediger.pl...@vodafone.com wrote:
Original-Nachricht
Betreff: svn commit: r1202257 - in /httpd/httpd/trunk/server/mpm/event:
config3.m4 equeue.c equeue.h event.c
Datum: Tue, 15 Nov 2011 15:51:04 GMT
Von: pque...@apache.org
On Wed, Nov 16, 2011 at 2:44 AM, Rainer Jung rainer.j...@kippdata.de wrote:
On 15.11.2011 20:57, Jeff Trawick wrote:
On Tue, Nov 15, 2011 at 2:32 PM, William A. Rowe Jr.
wr...@rowe-clan.net wrote:
On 11/15/2011 12:33 PM, Stefan Fritsch wrote:
On Tuesday 15 November 2011, Paul Querna wrote
Tend to agree with the other comments, NPN by itself will be
deprecated quickly, ALPN is the future. I'd vote for a series of back
ports that include both NPN and ALPN together.
On Mon, Apr 28, 2014 at 2:50 PM, Jim Jagielski j...@jagunet.com wrote:
Any reason to NOT include
Right now it is a beast of C++ code. I'd vote separate repo, take
learnings from it as a basis for HTTP/2.0.
On Wed, Apr 30, 2014 at 9:51 AM, Jim Jagielski j...@jagunet.com wrote:
I'm thinking... we should likely create a sep mod_spdy
repo (ala http://svn.apache.org/viewvc/httpd/mod_fcgid/)
- I think it is good to fix this behavior, using only the global
keepalive timeout was definitely a choice I (?) made when doing it.
- Skiplists seem generally acceptable for storing this data.
Alternatively a BTree with in order iteration would be competitive..
but, meh, either will be fine.
-
httpd side:
serf to me is the wrong question.
http/2.0 in the simplest implementation is just another protocol to
httpd. We have the constructs to handle it, kinda. Improvements to
async support in various bits will help.
However our constructs about requests and connections (and their
pools)
On Tue, Sep 23, 2014 at 12:45 PM, Jim Jagielski j...@jagunet.com wrote:
APR:
Considering that before we know it, http/2.0 will
be here, and ignoring httpd for the time being,
what features/additions do we see as being needed
to support http/2.0 from an APR library level? How do
we compare w/
Can you describe lagging in more detail?
None of the poll related code has a high rate of change (except for the
relatively new z/OS backend):
https://github.com/apache/apr/tree/trunk/poll/unix
Also are you looking specifically on Linux? (epoll backend?) or others
On Mon, Mar 9, 2015 at 11:04
right, libuv[1] is a good example of an IO completion API[2] that works
across both epoll/kqueue and IOCP. There have been a couple offhand
discussions about libuv on httpd-dev, but no one is clamoring for adoption.
APR currently has no such abstraction.
pollcb was added to provide a polling
It seems reasonable to focus on ALPN support, and generally dropping
NPN from trunk. NPN is already on a decline, and won't be used going
forward.
On Thu, Apr 2, 2015 at 12:44 AM, Stefan Eissing
stefan.eiss...@greenbytes.de wrote:
Any reason to differ from trunk in 2.4?
The people using spdy
On Mon, Oct 19, 2015 at 7:54 AM, Nick Kew wrote:
> On Mon, 19 Oct 2015 15:39:06 +0200
> Graham Leggett wrote:
>
>> > Note, mod_transform is GPL. Originally my decision when I released
>> > its earlier predecessor, before I was part of the dev@httpd team.
>> >
Saw this today, and noticed they used httpd as one of the projects they
collected data about:
http://neverworkintheory.org/2016/06/09/too-many-knobs.html
http://cseweb.ucsd.edu/~tixu/papers/fse15.pdf
Hard to make a quick conclusion, but I do believe in the general statement
of enumerations >
On Tue, Mar 22, 2016 at 3:32 PM, Yann Ylavic <ylavic@gmail.com> wrote:
> On Tue, Mar 22, 2016 at 4:18 PM, Paul Querna <p...@querna.org> wrote:
> > My thought was to add support for either multiple files, or multiple
> values
> > in the existing `SSLSessionTic
My thought was to add support for either multiple files, or multiple values
in the existing `SSLSessionTicketKeyFile`. Then add support to decrypt
from any of the known keys, and have a setting (or the first loaded key)
would be used to encrypt all new keys. This would allow for rotation in a
; I do not actually know what the serf support adds to httpd, it seems mostly
> some "SerfCluster" feature for mod_proxy. There's no docs and some comments
> in the code indicate the impl is not complete. SVN logs point to the same
> direction.
>
> Paul Querna wrote in his 2009 s
FTR I support moving to this versioning model.
I tend to think the best way to accomplish it, is to "just start doing
it". Tag 2.6.0. Then tag 2.7.0 when there are new features, etc.
Of course, our versioning docs don't support this model, but the docs
are a reflection of reality 15 years ago
I believe having more minor releases and less major backports to patch
releases is a good thing.
I believe we gave the even/odd, 2.1/2.3 "unstable", thing a long run.
About 15 years of it.
Since then the wider open source world has gone to a more canonical
semver. I think we should generally
Morning dev@,
I just committed mod_log_json to trunk in r1829898.
Right now, to use it you need something like this:
LogFormat "%^JS" json
CustomLog "logs/access_log.json" json
Currently it has a static format of the JSON, and example message is like this:
{
"log_id": null,
On Mon, Apr 23, 2018 at 10:10 AM, Micha Lenk wrote:
> On 04/23/2018 06:33 PM, William A Rowe Jr wrote:
>>
>> On Mon, Apr 23, 2018 at 11:12 AM, Micha Lenk wrote:
>>>
>>> On Fri, Apr 20, 2018 at 08:54:09AM -0400, Jim Jagielski wrote:
We have a history,
On Mon, Apr 23, 2018 at 11:17 AM, Christophe Jaillet
wrote:
> Le 23/04/2018 à 16:00, Jim Jagielski a écrit :
>>
>> It seems that, IMO, if there was not so much concern about "regressions"
>> in releases, this whole revisit-versioning debate would not have come up.
Years ago I started hacking on an "mpm fuzz":
https://github.com/pquerna/httpd/compare/trunk...pquerna:mpm_fuzz
The idea was to make a "fake" MPM, which could feed data from AFL directly
into the network filter stack, in a super efficient way.
I don't know if it is really a great idea, since TLS
James Park (pencil_ethics) wrote:
.
Unfortunately, since 1) I'm not a committer (and never will be),
This may sound crazy, but as someone who only marginally pays attention
to mod_aspdotnet and this mailing list, why would you say you will never
be a committer?
Committership offers are
Maxime Petazzoni wrote:
...
* XSLT processing
As far as I remember, the choice of outputting XML satisfies
everybody. The problem relates to where we'll do the XSLT
processing. There are two main solutions :
- client-side processing, as by now. The user requires a capable
browser such
is there any benchmarking tool that does Digest Authentication?
As far as I can see ab, flood and all others that I can find on google, just
do basic auth.
Is anyone interested in writing digest authentication abilities into flood?
-chip
901 - 928 of 928 matches
Mail list logo