Re: [users@httpd] apache 2.2.7 bit level info

In addition, it is also useful to add "-xarch=native and -xcode=pic32" to CFLAGS -xcode=pic32 helps linking with .so libraries which are not solaris-savvy (the equivalent of linux's -G / -fPIC) -xarch=native will optimise the code for the same machine it is compiling on (good if all your machines

Re: [users@httpd] Apache 2.4 - non adoption reasons??

Apache 2.4 is technically better and many commonly use components have been pulled into the Apache core, which had to be manually compiled before, but pulling in some modules and changing them for Apache 2.4 broke compatibility with said external modules, ie. importing mod_proxy_html but not mod_pr

Re: [users@httpd] Enabling ECDHE ciphers

*16-November-2013 Changes with Apache 2.2.26 (legacy)* ASF changes: *) mod_ssl: enable support for ECC keys and ECDH ciphers. Tested against OpenSSL 1.0.0b3. [Vipul Gupta, Sander Temme, Stefan Fritsch] So you need something at least 2.2.26 (the ECDH changes were backported from 2.4) We

Re: [users@httpd] mod_proxy unleashes hell on my server

Wow. Don't be a free anonomizing proxy for the Internet.. The suggestion about running a reverse proxy seems the best, but you must not allow forward proxy for everybody ! If you have a fixed internet ip, then this can make your fixed ip unusable, as once an open proxy is detected once, hundreds o

Re: [users@httpd] Httpd vhosts and ProxyPass/ProxyPassReverse and AJP - am I on crack?

You might need to change the names that the tomcat servers think of them selves as being. ie. call one server http://a.FOO.com and the other http://b.FOO.com Proxy pass reverse matches the first-hit right argument, again

[users@httpd] feature request for mod_remoteip

Hello, It would be nice if in mod_remoteip, you could specify a list of headers and not just one. eg: RemoteIPHeader X-Forwarded-For, X-Forward RemoteIPTrustedProxy 10.0.2.0/24 RemoteIPTrustedProxy gateway.localdomain Headers would preferably to be checked for in the provided order. Use case is

Re: [users@httpd] apache 2.4 virtualhosts

On Fri, Mar 16, 2012 at 6:41 PM, Eric Covener wrote: >> I'm just saying the documentation of the new matching scheme is >> deceptive, not that any code should be changed.. > > Operative point I'm trying to make is that there should not be a new > matching scheme -- at best only new doc that didn't

Re: [users@httpd] apache 2.4 virtualhosts

On Fri, Mar 16, 2012 at 12:38 AM, Eric Covener wrote: >> In your example it checks in the virtual hosts matching ip:port in >> config file order : >> >> 1. ServerName www.example.com >> >> 2. ServerName gone.example.com >> >> 3. ServerName forbidden.example.com >>    ServerAlias *.example.com >> >

Re: [users@httpd] apache 2.4 virtualhosts

Is order significant ? In your example it checks in the virtual hosts matching ip:port in config file order : 1. ServerName www.example.com 2. ServerName gone.example.com 3. ServerName forbidden.example.com ServerAlias *.example.com The wildcard is last in your example, in mine it is first

Re: [users@httpd] apache 2.4 virtualhosts

On Thu, Mar 15, 2012 at 7:37 PM, Tom Evans wrote: >> Ideally i'd like to do something like (whihc i could do in apache 2.2 >> - by virtue of NameVirtualHost, and grouping by IP with one as the >> default) : >> >> # serve a "we dont host this web site error message" by default for >> *.example.com

[users@httpd] ProxyExpressEnable

In apache 2.4 i'd like to use the new ProxyExpressEnable on a wildcarded VirtualHost, and put a some more specific VirtualHosts for reverse proxies which have more specific configurations or customizations, not provided by the default ProxyExpress reverse proxy behaviour. But ProxyExpressEnable do

[users@httpd] apache 2.4 virtualhosts

Hello, There is an example at : http://httpd.apache.org/docs/2.4/vhosts/name-based.html # This first-listed virtual host is also the default for *:80 ServerName www.example.com ServerAlias example.com *.example.com DocumentRoot /www/domain ServerName other.example.com DocumentRoot /www/otherd