Jeffrey,
are you sure you didn't miss anything ?
The following worked for me (I reproduced your scenario as I understood it,
build under /apps/apache_2.4.8, the cp -a to /apps/apache_2.4.8_int):
creith@hamlet:/apps/apache_2.4.8_int/bin$ sudo sed -i
's#/apps/apache_2.4.8#/apps/apache_2.4.8_int
On Tue, Sep 21, 2021 at 2:29 PM Jeff Cauhape wrote:
>
> Folks,
>
>
>
> When I built 2.4.48 from source, I built it in /apps/apache_2.4.48 directory.
> However, because of the way
>
> our servers are managed, I need to install this as /apps/apache_2.4.48_int
> and /apps/apache_2.4.48_ext.
>
> Whe
The host I'm using was originally named accordingly with the task
assigned back then, now one of the vhosts has the same name.
But, after noticed the issue just renamed the conf, and now everything
is working as expected.
Thank you all for your time and patience.-
El 2021-09-21 19:51, Fran
I would not rely on the debian scripts. Looking at apachectl -S will tell
you what you need to know.
On Tue, 21 Sept 2021 at 18:51, Frank Gingras wrote:
> Why do you have two vhosts with the same ServerName value set? That will
> break name-based vhosts. Set a unique ServerName value for every v
Carsten,
I use the first method you describe. It's always been pretty simple to
modify the pathnames before.
I can see how the multiple source trees/build targets would work, but the
problem is that some systems would require 4 build targets. I'd like to
keep it simple by have just 1 build targ
Why do you have two vhosts with the same ServerName value set? That will
break name-based vhosts. Set a unique ServerName value for every vhost on
that port.
On Tue, 21 Sept 2021 at 18:25, Daniel Armando Rodriguez
wrote:
> Here it is the curl result from the same host
>
> # curl -v -H Host:4.DOM
On 2021-09-21 6:25 p.m., Daniel Armando Rodriguez wrote:
Here it is the curl result from the same host
[snip]
From apachectl -S I see the problem is related to what vhost is set as
default
VirtualHost configuration:
*:80 is a NameVirtualHost
default server 4.DOM
Here it is the curl result from the same host
# curl -v -H Host:4.DOMAIN.edu.ar http://INTERNAL-IP/
* Expire in 0 ms for 6 (transfer 0x5573684c6c10)
* Trying INTERNAL-IP...
* TCP_NODELAY set
* Expire in 200 ms for 4 (transfer 0x5573684c6c10)
* Connected to INTERNAL-IP (INTERNAL-IP) port 80 (#0)
Show the httpd -S output and results from your tests with curl, then.
It might help to log the host: header in your access log too.
On Tue, 21 Sept 2021 at 17:41, Daniel Armando Rodriguez
wrote:
> Changed all vhosts definition the way you suggested, but the issue still
> happens.
>
>
> El 2021-
Changed all vhosts definition the way you suggested, but the issue still
happens.
El 2021-09-21 16:32, Frank Gingras escribió:
The first mistake is to use the hostnames when defining vhosts. Define
them all as *:PORT, then test with curl, and run apachectl -S or httpd
-S to spot any overlap.
El 2021-09-21 16:47, Darryl Philip Baker escribió:
I have ~200 virtualhosts on my Apache HTTPD server and all use the
declaration “” with not port specification. Just a
“Listen 80” directive. Do you specify the port on the VirtualHost
directive because you don’t want to accept traffic on all the
Hi,
what do you do exactly ?
- Do you build it with configure --prefix=/apps/apache_2.4.48 - make - make
install and then copy it to the two target directories ?
- Or do you build it two times modifiying the --prefix appropriately ?
I would strongly suggest to install it the second way. Or mayb
Darryl,
You can use * without the port under one specific condition:
You only listen to a single TLS or non-TLS port, and all vhosts are
configured to accept the traffic accordingly
Otherwise, you risk overlapping TLS and non-TLS vhosts, and your vhost will
not function properly.
On Tue, 21 Sep
2 things you can do. :
On the tomcat side of things, for the connector try this setting:
maxThreads="500"
The default is only 200 if not specified. Definitions can be found here:
https://tomcat.apache.org/tomcat-9.0-doc/config/http.html
On the apache webserver side of things you may need to make
I have some virtual hosts with well over 100 redirects and I have not seen a
user perceptible performance difference. I am sure there will be a machine
measurable different between the time it takes for the first redirect versus
the last but it doesn't affect the user experience.
Darryl Baker,
Hi,
Le 20/09/2021 à 18:29, Dave Wreski a écrit :
Hi,
At what point does it begin to affect performance with the number of
redirects and rewrites being used on a website? Have there been any
performance studies on this?
I've never seen such benchmark up to now.
We have a website (linuxsec
I have ~200 virtualhosts on my Apache HTTPD server and all use the declaration
“” with not port specification. Just a “Listen 80” directive. Do
you specify the port on the VirtualHost directive because you don’t want to
accept traffic on all the ports there are Listen directives for?
Darryl Bak
The first mistake is to use the hostnames when defining vhosts. Define them
all as *:PORT, then test with curl, and run apachectl -S or httpd -S to
spot any overlap.
On Tue, 21 Sept 2021 at 14:48, Daniel Armando Rodriguez
wrote:
> Hi,
>
> I have four subdomains on the same host which work as exp
Hi,
I have four subdomains on the same host which work as expected whis this
base config
ServerName 4.DOMAIN.edu.ar
ServerAlias 4.DOMAIN.edu.ar
ServerAdmin webmas...@domain.edu.ar
DocumentRoot /var/www/4
Options FollowSymLinks
AllowOverride All
Require all granted
Folks,
When I built 2.4.48 from source, I built it in /apps/apache_2.4.48 directory.
However, because of the way
our servers are managed, I need to install this as /apps/apache_2.4.48_int and
/apps/apache_2.4.48_ext.
When I have done this for earlier versions of Apache, I just edited the path
n
Hi all,
I have the Apache proxy module reporting "AH00898: Error reading from remote
server" on high load.
Any recommendations for what params should I need to review on the proxy config
or on the connector side (Tomcat)?
Thanks for your help
Israel
--
21 matches
Mail list logo
