Re: [users@httpd] http2

2018-03-28 Thread David Mehler
Hello, First Frank thanks. Switching from prefork to event, I can tell the difference. I've got working http2 which is great! I disabled mod_php and enabled php-fpm, if I request a file: test.example.com/file.php works fine, if I just go to: test.example.com or really any other virtual host

Re: [users@httpd] http2

2018-03-28 Thread Frank Gingras
You need to use a threaded mpm (event or worker) to support http2. Additionally, you need to configure httpd to use fcgi to process php content. See http://wiki.apache.org/httpd/php The simplest approach will likely to use mod_proxy_fcgi and php-fpm pools. On Wed, Mar 28, 2018 at 12:17 PM, David

[users@httpd] http2

2018-03-28 Thread David Mehler
Hello, Currently I'm running Apache 2.4, openssl, Php 5.6, mod_php, and with apache the prefork mpm. my mpm from prefork to either worker or event. What is the difference between these two mpms? It appears i'm also going to have to make a php change, threaded php, should I move to php7, does that

Re: [users@httpd] TLS 1.3

2018-03-28 Thread Daniel Ferradal
briefly -> "some benefits that involve some problems that need the server to support something to prevent them" And now more seriously I read a quick explanation on the benefits on twitter yesterday, I'm sure there are more authorizative sources but it seems like a quick way to catch up if you are

Re: [users@httpd] TLS 1.3

2018-03-28 Thread David Mehler
Hi, I didn't know TLS 1.3 was out, thought it was next year before we'd see it. What are some advantages of 1.3? Thanks. Dave. On 3/28/18, Stefan Eissing wrote: > Glad you asked: I just committed r1827912 into trunk that adds support for > TLSv1.3 when linking against OpenSSL v.1.1.1-pre3. Thi

Re: [users@httpd] mod_allowmethods to get all the http methods working

2018-03-28 Thread Nick Kew
On Wed, 2018-03-28 at 13:17 +0200, Francesco Piraneo G. wrote: > After a lot of googling and asking to other colleagues I finally > arrived at mod_allowmethods so I changed my configuration in the > following way: Looks like a red herring to me. What you need is your handler to *support* the met

Re: [users@httpd] mod_allowmethods to get all the http methods working

2018-03-28 Thread Daniel Ferradal
Hello, You need to check two things. * Are you really landing in that virtualhost? Check "apachectl -S" output for the virtualhosts you have. Make sure there are no duplicate servernames used in different virtualhosts and that prior virtualhost witout servername or a greedy serveralias is not cat

Re: [users@httpd] mod_allowmethods to get all the http methods working

2018-03-28 Thread Francesco Piraneo G.
Sorry... I forgot a relevant part of my question: What's happens! (hard day today) When I try to access to the api with the PUT or DELETE method, Apache2 answer with: 192.168.1.22 - - [28/Mar/2018:11:09:06 +0200] "PUT /group/users/ HTTP/1.1" *405* 489 "-" "PostmanRuntime/7.1.1" (Basically

Re: [users@httpd] TLS 1.3

2018-03-28 Thread Stefan Eissing
Glad you asked: I just committed r1827912 into trunk that adds support for TLSv1.3 when linking against OpenSSL v.1.1.1-pre3. This does allow TLSv1.3 clients to talk that version to the server, but it will not enable any fancy early data or such. There is more support needed in the server to pro

[users@httpd] mod_allowmethods to get all the http methods working

2018-03-28 Thread Francesco Piraneo G.
Hi all, I'm developing a REST api based on PHP 7.1 and Apache 2.4 (under ubuntu 17.10). The api requires the following methods working: GET POST OPTIONS PUT DELETE After a lot of googling and asking to other colleagues I finally arrived at mod_allowmethods so I changed my configuration in th

Re: [users@httpd] Apache HTTP Server 2.4.33 (httpd) installed on CentOS7.4

2018-03-28 Thread Stefan Eissing
Thanks, Kazuhiko. Always nice to get feedback. Cheers, Stefan > Am 28.03.2018 um 03:21 schrieb kohmoto : > > Hi, > > OS: CentOS7.4.1708 > kernel: 3.10.0-693.21.1 > > > Apache HTTP Server 2.4.33 has been installed successfully via rpmbuild on > CentOS7.4. > Thank you all for building this nic