RE: [users@httpd] Mod_proxy_balancer question

2017-05-15 Thread Hristiyan Kirov
Hello, Looks OK, however I’ve seen it defined like this: BalancerMember ajp://host1:8018 route=host1 BalancerMember ajp://host2:8018 route=host2 ProxyPass /foo balancer://cluster/foo Regards, Hristiyan From: Kartik Vashishta [mailto:kartik.u...@gmail.com] Sent:

Re: [users@httpd] How to customize error responses (while using mod_rewrite)?

2017-05-15 Thread Marat Khalili
Just in case you are stuck, you can always use internal redirect to a CGI script (or PHP or whatever) and write whatever response you want with that script. It's kind of cheating but it should work. -- With Best Regards, Marat Khalili On May 15, 2017 5:46:52 PM GMT+03:00, Jens Schleusener wr

RE: [users@httpd] A curious thing - apachectl status in Apache 2.4.25

2017-05-15 Thread Jeff Cauhape
Rick, That could be, except that if I just gave the stop command and it's "still" running it doesn't nearly concern me as much as getting an Elinks error and wondering if it's because it isn't running or whether there is some other issue. Besides, this It's DEAD/ALIVE message comes _ after _ the

RE: [users@httpd] A curious thing - apachectl status in Apache 2.4.25

2017-05-15 Thread Houser, Rick
> I just added a couple of lines of shell script following the links command > after the 'status' command line switch. It checks for the number of httpd processes, and if there are none, it echoes "It's DEAD, Jim!". Otherwise It echoes "It's ALIVE!!!". Isn't that just going to give bad results,

RE: [users@httpd] A curious thing - apachectl status in Apache 2.4.25

2017-05-15 Thread Jeff Cauhape
Eric, Yes, I went from 2.4.6 bundled with Red Hat to a plain source code build. It didn't occur to me that it might be that simple. Thanks! :o Mgmt has decided that they want the ability to easily have multiple versions of Apache on our servers and to be able to switch from one build to another b

[users@httpd] Re: How to customize error responses (while using mod_rewrite)?

2017-05-15 Thread Jens Schleusener
On Mon, 15 May 2017, Eric Covener wrote: On Mon, May 15, 2017 at 12:32 PM, Jens Schleusener wrote: Ok, in that case one could use the ErrorDocument directive (it works for me principally) but how can one can achieve that that directive is not used globally but only specific for the above case?

Re: [users@httpd] A curious thing - apachectl status in Apache 2.4.25

2017-05-15 Thread Eric Covener
On Mon, May 15, 2017 at 1:22 PM, Jeff Cauhape wrote: > In the Apache 2.4.6 shell script apachectl, a call to “apachectl status” > > invokes systemctl status httpd.service. This gives you easy-to-read > > output regardless if the server is running or not. Did you go from a vendor package to a sou

[users@httpd] A curious thing - apachectl status in Apache 2.4.25

2017-05-15 Thread Jeff Cauhape
I recently built Apache 2.4.25 and am running it on RHEL 7.3. I've found something that seems a step backwards from 2.4.6 and I'm hoping someone can shed some light on it. In the Apache 2.4.6 shell script apachectl, a call to "apachectl status" invokes systemctl status httpd.service. This gives y

Re: [users@httpd] Re: How to customize error responses (while using mod_rewrite)?

2017-05-15 Thread Eric Covener
On Mon, May 15, 2017 at 12:32 PM, Jens Schleusener wrote: > Ok, in that case one could use the ErrorDocument directive (it works for me > principally) but how can one can achieve that that directive is not used > globally but only specific for the above case? > > The idea to set in the above Rewri

[users@httpd] Mod_proxy_balancer question

2017-05-15 Thread Kartik Vashishta
Hi, We are using httpd 2.2 and wonder if a path to the application can be defined in the BalanceMember definition, so would this work: BalanceMember "http://192.168.1.50:/foo/bar"; route=node1

[users@httpd] Re: How to customize error responses (while using mod_rewrite)?

2017-05-15 Thread Jens Schleusener
On Mon, 15 May 2017, Eric Covener wrote: On Mon, May 15, 2017 at 10:46 AM, Jens Schleusener wrote: Unfortunately for the RewriteRule directive for e.g. a Rewrite flag R=4xx instead of R=permanent isn't allowed (only 300-399, why?) so I had considered the usage of the directive but didn't find

Re: [users@httpd] Redirect all unconfigured sub-domains to specific sub-domain

2017-05-15 Thread James Smith
You really only have one option at the moment and that is to pay for a wild card certificate which will do this {lets encrypt doesn't allow you yet} It will probably set you back something like 100$ a year o/w you will need to set your redirects up from xxx. to https:// individually a

[users@httpd] Redirect all unconfigured sub-domains to specific sub-domain

2017-05-15 Thread Torge Riedel
Hi, I'm using Apache 2.2 and currently have the following configuration files: 00-default-> redirect non-https-URLs to https-URLs 00-default-ssl -> default configuration for https://mydomain.de and https://www.mydomain.de Then several files 20-sub.mydomain.de

Re: [users@httpd] mod_proxy and 404

2017-05-15 Thread Felipe Gasper
> On 15 May 2017, at 11:13 AM, Eric Covener wrote: > > On Mon, May 15, 2017 at 11:06 AM, Felipe Gasper > wrote: >>I’m noticing that mod_proxy sends its entire payload upstream without >> checking for an early response (e.g., 308 or 404). If upstream sends such a >> response then clos

[users@httpd] How to proxy web server?

2017-05-15 Thread Florian Lindner
Hello, Apache 2.4 on Debian Testing, mpm_itk I have the Discourse web forum running in a docker container. The container's webserver is bount to localhost:2080. The forum should be reachable at either forum.csc-stuttgart.org or csc-stuttgart.org/forum. Possibility A: ServerName forum

Re: [users@httpd] mod_proxy and 404

2017-05-15 Thread Eric Covener
On Mon, May 15, 2017 at 11:06 AM, Felipe Gasper wrote: > I’m noticing that mod_proxy sends its entire payload upstream without > checking for an early response (e.g., 308 or 404). If upstream sends such a > response then closes the connection, mod_proxy never sees it and reports a > 502

[users@httpd] mod_proxy and 404

2017-05-15 Thread Felipe Gasper
Hello, I’m noticing that mod_proxy sends its entire payload upstream without checking for an early response (e.g., 308 or 404). If upstream sends such a response then closes the connection, mod_proxy never sees it and reports a 502 back. Browsers don’t behave this way; they see

Re: [users@httpd] How to customize error responses (while using mod_rewrite)?

2017-05-15 Thread Eric Covener
On Mon, May 15, 2017 at 10:46 AM, Jens Schleusener wrote: > Unfortunately for the RewriteRule directive for e.g. a Rewrite flag R=4xx > instead of R=permanent isn't allowed (only 300-399, why?) so I had > considered the usage of the directive but didn't find a working > solution. Other codes are

[users@httpd] How to customize error responses (while using mod_rewrite)?

2017-05-15 Thread Jens Schleusener
Hi, my general question is how I can generate customized error responses while using the mod_rewrite module. Yes, I know the page https://httpd.apache.org/docs/2.4/custom-error.html but the ErrorDocument directive allows only to do some customization per status code optionally refined by co

Re: [users@httpd] Getting PHP-FPM working

2017-05-15 Thread John Iliffe
Hi Christian: I just noticed that you put "" around the parameters to ProxyPassMatch. I tried that and no change in the results. John On Monday 15 May 2017 05:21:59 Christian Hettler wrote: > Hello John, > > the manual (mod_proxy_fcgi.html) states: > > "The req

Re: [users@httpd] Getting PHP-FPM working

2017-05-15 Thread John Iliffe
Thank you for your suggestion Christian. Same result. (there are no passed parameters to the script being invoked). httpd.conf: ProxyPassMatch ^/.*\.php(/.*)?$ fcgi://127.0.0.1:9015/httpd/iliffe/ Browser: No input file specified. Apache error log: [Mon May 15 10:12:2

Re: [users@httpd] Getting PHP-FPM working

2017-05-15 Thread Christian Hettler
Hello John, the manual (mod_proxy_fcgi.html) states: "The request URL is implicitly added to the 2nd parameter." (Did|Can) you try ProxyPassMatch "^/.*\.php(/.*)?$" "fcgi://127.0.0.1:9015/httpd/iliffe/" instead of > # ProxyPassMatch ^/(.*\.php(/.*)?)$ fcgi://127.0.0.1:9015/httpd/iliffe/$1