Re: svn commit: r1899552 - in /httpd/httpd/trunk: modules/http/ modules/proxy/ test/modules/http1/ test/modules/http1/htdocs/ test/modules/http1/htdocs/cgi/ test/modules/http1/htdocs/cgi/files/ test/m

> Am 04.04.2022 um 16:07 schrieb Ruediger Pluem : > > > > On 4/4/22 1:08 PM, ic...@apache.org wrote: >> Author: icing >> Date: Mon Apr 4 11:08:58 2022 >> New Revision: 1899552 >> >> URL: http://svn.apache.org/viewvc?rev=1899552=rev >> Log: >> *) mod_http: genereate HEADERS buckets for

Re: svn commit: r1899552 - in /httpd/httpd/trunk: modules/http/ modules/proxy/ test/modules/http1/ test/modules/http1/htdocs/ test/modules/http1/htdocs/cgi/ test/modules/http1/htdocs/cgi/files/ test/m

> Am 05.04.2022 um 09:34 schrieb Ruediger Pluem : > > > > On 4/5/22 9:13 AM, Stefan Eissing wrote: >> >> >>> Am 04.04.2022 um 16:07 schrieb Ruediger Pluem : >>> >>> >>> >>> On 4/4/22 1:08 PM, ic...@apache.org wrote: Author: icing Date: Mon Apr 4 11:08:58 2022 New

Re: svn commit: r1899552 - in /httpd/httpd/trunk: modules/http/ modules/proxy/ test/modules/http1/ test/modules/http1/htdocs/ test/modules/http1/htdocs/cgi/ test/modules/http1/htdocs/cgi/files/ test/m

> Am 05.04.2022 um 10:20 schrieb Ruediger Pluem : > > > > On 4/5/22 9:53 AM, Stefan Eissing wrote: >> >> >>> Am 05.04.2022 um 09:34 schrieb Ruediger Pluem : >>> >>> >>> >>> On 4/5/22 9:13 AM, Stefan Eissing wrote: > Am 04.04.2022 um 16:07 schrieb Ruediger Pluem : >

Re: svn commit: r1899552 - in /httpd/httpd/trunk: modules/http/ modules/proxy/ test/modules/http1/ test/modules/http1/htdocs/ test/modules/http1/htdocs/cgi/ test/modules/http1/htdocs/cgi/files/ test/m

On 4/5/22 9:13 AM, Stefan Eissing wrote: > > >> Am 04.04.2022 um 16:07 schrieb Ruediger Pluem : >> >> >> >> On 4/4/22 1:08 PM, ic...@apache.org wrote: >>> Author: icing >>> Date: Mon Apr 4 11:08:58 2022 >>> New Revision: 1899552 >>> >>> URL: http://svn.apache.org/viewvc?rev=1899552=rev >>>

Re: svn commit: r1899390 - in /httpd/httpd/trunk: CHANGES modules/proxy/mod_proxy.c modules/proxy/mod_proxy.h

On 01/04/2022 13:41, Jim Jagielski wrote: It was added in anticipation of the capability to be folded in, and done so "now" so that it would;t require any API changes. Unless it's actually breaking something, I'd vote to simply keep it OK I will try to propose some code to create the

Re: svn commit: r1899552 - in /httpd/httpd/trunk: modules/http/ modules/proxy/ test/modules/http1/ test/modules/http1/htdocs/ test/modules/http1/htdocs/cgi/ test/modules/http1/htdocs/cgi/files/ test/m

On 4/5/22 9:53 AM, Stefan Eissing wrote: > > >> Am 05.04.2022 um 09:34 schrieb Ruediger Pluem : >> >> >> >> On 4/5/22 9:13 AM, Stefan Eissing wrote: >>> >>> Am 04.04.2022 um 16:07 schrieb Ruediger Pluem : On 4/4/22 1:08 PM, ic...@apache.org wrote: > Author: icing

Re: Current status of mod_h2 test suite?

Hi Stefan, Am 05.04.2022 um 13:49 schrieb Stefan Eissing: Which test suite, the one in trunk or the one from github? Both work best against the respective source. the test suite in https://svn.apache.org/repos/asf/httpd/test/mod_h2/trunk Which one would you recommend to test http2 in a

Re: Current status of mod_h2 test suite?

Thaks, will switch to that one. Should have reembered it ... Am 05.04.2022 um 14:04 schrieb Stefan Eissing: Am 05.04.2022 um 14:01 schrieb Rainer Jung : Hi Stefan, Am 05.04.2022 um 13:49 schrieb Stefan Eissing: Which test suite, the one in trunk or the one from github? Both work best

Re: Current status of mod_h2 test suite?

> Am 05.04.2022 um 14:08 schrieb Rainer Jung : > > Thaks, will switch to that one. Should have reembered it ... All fine. Hit me with questions if it gives you problems. > > Am 05.04.2022 um 14:04 schrieb Stefan Eissing: >>> Am 05.04.2022 um 14:01 schrieb Rainer Jung : >>> >>> Hi Stefan,

Re: Serve multiple websites (not sub-domains) from port 80

You should use Name based hosting and that will serve your purpose. On Mon, Apr 4, 2022 at 8:48 PM A wrote: > Hi, > > I am planning to make changes to Apache web server so that it can serve > multiple websites (not sub-domains) from port 80. > > This will save money for someone who has more

Current status of mod_h2 test suite?

I try to make the mod_h2 test suite run for me. Some difficulties are expected due to my non-standard setup, but the first test that seems to fail in a way I am not directly blaming myself is fuzz header * on http://test.example.org:12345: super-long...--- gen/expect_431 2022-04-05

Re: Current status of mod_h2 test suite?

> Am 05.04.2022 um 14:01 schrieb Rainer Jung : > > Hi Stefan, > > Am 05.04.2022 um 13:49 schrieb Stefan Eissing: >> Which test suite, the one in trunk or the one from github? Both work best >> against the respective source. > > the test suite in > >

Re: Current status of mod_h2 test suite?

Which test suite, the one in trunk or the one from github? Both work best against the respective source. > Am 05.04.2022 um 13:47 schrieb Rainer Jung : > > I try to make the mod_h2 test suite run for me. Some difficulties are > expected due to my non-standard setup, but the first test that