Re: [users@httpd] https not working

2018-06-20 Thread Alex K
Hi, Have you enabled ssl and rewrite modules? I would verify also that there is no firewall blocking 443. Alex On Wed, Jun 20, 2018, 18:24 Mahmood Naderan wrote: > Hi, > My web site works on http without any problem. The location is > /var/www/html/shob/ and I want to define an HTTPS

Re: [users@httpd] mod_proxy_http rewrite problem

2018-06-20 Thread Herb Burnswell
It works It works with the ProxyPassReverse included. Yann - Thank you very much for all of your help, it's greatly appreciated.. Best, HB On Wed, Jun 20, 2018 at 7:54 AM, Yann Ylavic wrote: > On Tue, Jun 19, 2018 at 11:26 PM, Herb Burnswell > wrote: > > > > Attached is the error_log

[users@httpd] Apache site conf Include not working

2018-06-20 Thread Ian Gilbert
Hi, I am using Apache 2.4.18 on ubuntu x64. I have a large site config with many rewrites and want to split them off into multiple conf files using Include. They all work perfectly in one single file When I add an include inside a VirtualHost, the included file is not used. The syntax is

[users@httpd] Slow Apache 2.4 server

2018-06-20 Thread Jørn
Hello, I have a problem with slow access from Apache 2.4.27 (new server) compared to an older Apache 2.2.14 (old server. The old server is a dual core AMD running Fedora Core 12 with 4Gb physical memory, while the new server is an 8 core AMD with 16 Gb memory. It is the same PHP code on

[users@httpd] https not working

2018-06-20 Thread Mahmood Naderan
Hi,My web site works on http without any problem. The location is /var/www/html/shob/ and I want to define an HTTPS virtualhost. So, I COPIED the content relative to my website from /etc/apach2/sites-available/000-default.conf  to /etc/apache2/sites-available/default-ssl.conf and the content

Re: [users@httpd] mod_proxy_http rewrite problem

2018-06-20 Thread Yann Ylavic
On Tue, Jun 19, 2018 at 11:26 PM, Herb Burnswell wrote: > > Attached is the error_log (scrubbed, may be some replace oddities, but you > can see the progression..). OK, it seems that the ProxyPass(es) order matters actually. How about: ProxyPass /frontpage/