I have a website in php running on apache server.
1) How can I configure it so that it runs with a URL like abc.com
2) How can I configure it so that it runs with a subdomain
like x.abc.com, y.abc.com, z.abc.com etc and so on.
I should not have to add a new entry in config files to add a new
1) How can I configure it so that it runs with a
URL like abc.com
See the documentation. If you need screen shots
and much and holding, see Google.
I should not have to add a new entry in config
files to add a new subdomain.
See your web hosting company. If you're not
comfortable
My environment is affected by bug 40047, the lack of a mod_proxy_ajp
equivalent to mod_jk's JkEnvVar directive. (The mod_rewrite gyrations
required to work around this with AJP_* vars are too unpleasant to
maintain.) If I write a patch for this feature, might it stand a
chance of
On Wed, 27 Aug 2008 23:53:24 -0700
Ian Ward Comfort [EMAIL PROTECTED] wrote:
My environment is affected by bug 40047, the lack of a mod_proxy_ajp
equivalent to mod_jk's JkEnvVar directive. (The mod_rewrite
gyrations required to work around this with AJP_* vars are too
unpleasant to
| While reviewing the patch for PR41391
| (https://issues.apache.org/bugzilla/show_bug.cgi?id=41391),
| I noticed that besides a possible overflow, it could happen that the
| expires date is in the past
| (just take an old file and say modification plus 1 minute). What we really
| want to say
On Aug 28, 2008, at 6:15 AM, Nick Kew wrote:
On Wed, 27 Aug 2008 23:53:24 -0700
Ian Ward Comfort [EMAIL PROTECTED] wrote:
My environment is affected by bug 40047, the lack of a mod_proxy_ajp
equivalent to mod_jk's JkEnvVar directive. (The mod_rewrite
gyrations required to work around this
Den Wednesday 20 August 2008 12:06:33 skrev Oden Eriksson:
[...]
FYI: This patch is applied in Mandriva Linux.
However, the perl-framework tests barfs at:
t/ssl/v2# Failed test 1 in t/ssl/v2.t at line 16
--
Regards // Oden Eriksson
Oden Eriksson wrote:
However, the perl-framework tests barfs at:
t/ssl/v2# Failed test 1 in t/ssl/v2.t at line 16
The root cause for this failure could actually be the same as for a
different issue which was reported to me by private e-mail just
yesterday - in
I wrote:
When I added the second condition to the first if statement, I was
assuming that the default for auth.verify_depth is UNSET as well.
However, it's initialized to 1 (i.e. SSL_CVERIFY_OPTIONAL)
Wrong, of course - this macro
On 28 Aug 2008, at 3:15 AM, Nick Kew wrote:
How big is this proposed patch? A patch that can be reviewed in
five minutes has a lower barrier to inclusion than one that a
developer has to spend all day reviewing :-)
At the moment, it's just hypothetical, but mod_jk implements JkEnvVar
in
Hello,
I'm actually trying to setup a SSL reverse-proxy based on Apache 2.x and
mod_ssl and it seems there's a bug in the verification of the CRL.
If a CA changes its keys before expiration, the CRL is now signed by the
new key and include certificates issued by both the new and old keys.
I am looking for 2 things mod_proxy_balancer cannot currently provide:
1. Something to limit the maximum impact of having many dead members
under a load balancer on normal requests.
* The process of discovering that dead workers are still dead
shouldn't overtly impact
Making SNI support configurable at runtime also seems a more attractive
solution to me - it would basically mean that in ssl_init_ctx(), the SNI
callback is not registered unless it's explicitly configured. I would
suggest using something like
SSLEnableSNI port [port] ...
which would
13 matches
Mail list logo
