On 29 Jun 2020, at 10:16, Stefan Eissing wrote:
>> The main point is that it must be done carefully and properly, but this is
>> not a reason to not do it at all.
>
> Apache httpd is a very strong HTTP/1.x server. And your efforts to make
> response streaming more event driven have been
On Mon, Jun 29, 2020 at 1:17 AM Stefan Eissing
wrote:
> 2. Redesign a FOSS httpd v3.x with a new architecture, embracing a
> non-blocking processing model. Maybe under a different name.
Is there widespread interest in this approach (option 2)? It's, in
theory, my preference -- I get the
Build Update for apache/httpd
-
Build: #945
Status: Fixed
Duration: 7 mins and 47 secs
Commit: ec11716 (trunk)
Author: Graham Leggett
Message: Bump MMN correctly.
git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@1879479
Build Update for apache/httpd
-
Build: #944
Status: Broken
Duration: 26 mins and 35 secs
Commit: 6bf5bd6 (trunk)
Author: Graham Leggett
Message: core: Remove support for the Content-MD5 header, removed in RFC7231.
Functions ap_md5digest() and
Build Update for apache/httpd
-
Build: #942
Status: Fixed
Duration: 20 mins and 12 secs
Commit: d4c582b (trunk)
Author: Graham Leggett
Message: Add log numbers to util_etag.c.
git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@1879470
On 03 Jul 2020, at 11:19, Ruediger Pluem wrote:
> Thanks for the pointer. Is Content-MD5 really used? And given that it has
> been removed in the RFC my approach would be as follows:
>
> 1. Continue with your new additions as is. Do not try to merge any of this
> code with Content-MD5 related
Build Update for apache/httpd
-
Build: #941
Status: Still Failing
Duration: 12 mins and 4 secs
Commit: deb95b0 (trunk)
Author: Graham Leggett
Message: Seek to the start of the file when calculating the ETag.
git-svn-id:
On 7/3/20 10:54 AM, Graham Leggett wrote:
> On 29 Jun 2020, at 16:37, Ruediger Pluem wrote:
>
>> Makes sense.
>> Do you see a possibility to merge this code and the one of ap_md5digest to a
>> more generic procedure that
>> allows to choose the digest algorithm while using 'MMAPED' reads?
>>
On 03 Jul 2020, at 11:02, Ruediger Pluem wrote:
>> apr_sha1_init();
>> nbytes = sizeof(buf);
>> -while (apr_file_read(fd, buf, ) == APR_SUCCESS) {
>> +while ((status = apr_file_read(fd, buf, )) == APR_SUCCESS) {
>
> Don't we need to set the fp in fd via
Build Update for apache/httpd
-
Build: #940
Status: Broken
Duration: 19 mins and 29 secs
Commit: 06af945 (trunk)
Author: Graham Leggett
Message: mod_dav: Allow other DAV modules to use dav_get_resource().
git-svn-id:
On 7/3/20 10:21 AM, minf...@apache.org wrote:
> Author: minfrin
> Date: Fri Jul 3 08:21:13 2020
> New Revision: 1879465
>
> URL: http://svn.apache.org/viewvc?rev=1879465=rev
> Log:
> Be defensive when calculating the digest. Make sure the offset is initialised
> to zero before reading the
On 29 Jun 2020, at 16:37, Ruediger Pluem wrote:
> Makes sense.
> Do you see a possibility to merge this code and the one of ap_md5digest to a
> more generic procedure that
> allows to choose the digest algorithm while using 'MMAPED' reads?
> BTW: Is sha1 mandatory for strong etags? If not
12 matches
Mail list logo
