No matter which solution you choose, the real problem is to detect that the
server fails.
If the server stops responding to requests, that's easy enough. However if
there is not a clear-cut failure, e.g. one server gradually slows down, or
still responds to the polls from the load balancer but
ProxyPassReverseCookieDomain does not change the cookie name - only the domain
field of the cookie.
Use LiveHTTPHeaders on Mozilla or similar (like Ethereal, burpproxy...) to see
exactly what the browser receives (Set-Cookie header) and what it subsequently
sends to the server in terms of
Whenever possible I try to avoid modifying the URL path when reverse proxying.
Then mod_proxy_html is not needed and you save some CPU cycles.
Location /flickr
ProxyPass http://www.flickr.com/flickr
ProxyPassReverse http://www.flickr.com/flickr
/Location
-ascs
If I may inject a related question here, I was recently surprised to discover
the order in which rewrite rules are evaluated when using RewriteOptions
inherit in a VH. It seems like the rewrite rules included in the VH are
evaluated before the ones that are inherited.
Is that correct?
Is there
Somebody is probably reformatting your hard drive.
No, seriously you need to provide a LOT more information about your
configuration for anyone to get the foggiest idea about what causes this.
What HW/OS? Are these disk reads or writes? What kind of modules do you use?
PHP or no PHP? etc.
I
I explicitly set it to 0 for all of my servers. Never had a problem.
In my mind setting it to anything different than zero would just be a temporary
hack to circumvent a bug in some module, particularly memory leaks.
Various load tests I have made on Apache clearly show that restarting
Lalit,
Your WebSphere plugin XML configuration file probably does not contain any
configuration for port 9191. You need to add *:9191 to the list of addresses on
which the plugin will intercept requests. You do that by adding a VirtualHost
to the appropriate VirtualHostGroup in the plugin
Hi Michelle,
There are systems that allow you to authenticate a user, set a cryptographic
session cookie on the client browser and subsequently use that token to
authenticate the client sending the HTTP request. These systems also allow you
to define access control rules that depend on the
Is it possible that the directory is not writable to the Apache process owner??
If the server listens to ports below 1024 that's unlikely since it must start
as root and will have root privileges when creating the pid and log files, but
you never know...
-ascs
-Message d'origine-
De :
RewriteEngine on
RewriteCond %{QUERY_STRING} ^mid=(\d+)$
RewriteRule ^/movie_play.php /movie%1.html? [R]
-Message d'origine-
De : tech user [mailto:[EMAIL PROTECTED]
Envoyé : mardi 25 septembre 2007 08:18
À : users@httpd.apache.org
Objet : Re: [EMAIL PROTECTED] help about a rewrite
If you know what you are doing, you can turn on or more of the following cache
settings:
- CacheIgnoreCacheControl
- CacheIgnoreNoLastMod
AND limit the time during which the response may be cached with
- CacheMaxExpire
You should also add
- CacheIgnoreHeaders:
HTTPS and NameVirtualHost do not go well together. NVH is based on the Host
header. However Apache cannot read the Host header before the SSL session has
been established. But in order to establish the SSL session, Apache needs to
know what virtual host it is for to determine what certificate
Hi
Those of you who use mod_rewrite in a reverse-proxy scenario (RewriteRule with
the [P] flag) might be interested in
http://issues.apache.org/bugzilla/show_bug.cgi?id=43308.
In such a scenario mod_proxy will not be able to use persistent connections
(KeepAlive) to the origin server. This is
Why don't you try
Header set Referer
or,
Header unset Referer
Looks like the mod_header filter is executed pretty late in the request
processing, so that might do the trick.
-ascs
De : [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Envoyé : jeudi 6
;
}
-ascs
-Message d'origine-
De : Axel-Stéphane SMORGRAV
Envoyé : mercredi 29 août 2007 19:18
À : users@httpd.apache.org
Objet : [EMAIL PROTECTED] Apache 2.2.x mod_rewrite and mod_proxy and pooled
connections
Hello folks,
I have been doing some testing with Apache 2.2.4 recently
Hello folks,
I have been doing some testing with Apache 2.2.4 recently, and one of the
things I am particularly interested in is the pooling of backend connections of
mod_proxy's as this makes it possible to maintain persistent connections to
backend systems across requests from different
Ooops. :-)
-Original Message-
From: Robert Ionescu [mailto:[EMAIL PROTECTED]
Sent: Monday, July 10, 2006 11:52 PM
To: users@httpd.apache.org
Subject: Re: [EMAIL PROTECTED] Re: problem with mod_rewrite rewiterule with
[P](internal proxying)
Axel-Stéphane SMORGRAV wrote:
What does
You probably need to modify the access rights of the associated Directory
section accordingly.
I am not familiar with Apache on Win XP but I guess you need something like
Directory G:/tees
Options MultiViews
AllowOverride None
Order allow,deny
Allow from all
/Directory
-ascs
contact your friendly IBM representative.
-ascs
-Original Message-
From: Ravish Agarwal [mailto:[EMAIL PROTECTED]
Sent: Monday, July 10, 2006 11:20 AM
To: Axel-Stéphane SMORGRAV
Cc: users@httpd.apache.org
Subject: RE: [EMAIL PROTECTED] Re: problem with mod_rewrite rewiterule with
[P
Very strange... Apparently the list software omitted to insert the Reply-To
header.
-Original Message-
From: Axel-Stéphane SMORGRAV
Sent: Monday, July 10, 2006 8:23 AM
To: 'Ravish Agarwal'
Subject: RE: [EMAIL PROTECTED] Re: problem with mod_rewrite rewiterule with
[P](internal proxying
The rewrite logs included in the original post indicate that the proxying does
work, so that cannot possibly be the problem.
-ascs
-Original Message-
From: Joost de Heer [mailto:[EMAIL PROTECTED]
Sent: Friday, July 07, 2006 9:55 AM
To: Ravish Agarwal
Cc: users@httpd.apache.org
What does that have to do with this particular problem
-ascs
-Original Message-
From: Robert Ionescu [mailto:[EMAIL PROTECTED]
Sent: Friday, July 07, 2006 1:06 PM
To: users@httpd.apache.org
Subject: Re: [EMAIL PROTECTED] Re: problem with mod_rewrite rewiterule with
[P](internal
for apache 1.3
says but its not there at apache 2.0 manual page. I am using apache 2.0.55
Output of httpd -l shows the following
$ ./httpd -l
Compiled in modules:
core.c
worker.c
http_core.c
mod_so.c
I have the mod_proxy_http enabled too. So what could be the poblem?
On 7/7/06, Axel-Stéphane
It seems like there is some fundamental misunderstanding about HTTP and the
way the Siteminder WebAgents work.
Let mpe say a few words about the Web Agent.
When the WebAgent (SMWA) (which may either be an Apache module or an
application server plug-in known as TAI) receives a request for a
Could it possibly be for communication with a DNS server ? Have you tried
sniffing UDP packets sent to/from this port?
-ascs
-Original Message-
From: Richard de Vries [mailto:[EMAIL PROTECTED]
Sent: Wednesday, July 05, 2006 7:07 PM
To: users@httpd.apache.org
Subject: [EMAIL PROTECTED]
I ran a netstat on some of my apache server hosts looking for UDP sockets, but
could not find any. The only UDP sockets I could see were on the NTP port. Then
I tried lsof and could not find anything concerning httpd either.
I am therefore wondering whether you could possibly have a module that
Although this subject does not seem to be related to Apache, and I have not
been near HP-UX for years...
I had a look at the Siteminder WebAgent Installation guide. There is a section
called Enabling SHLIB Path for an Agent on Apache2/HP-UX 11 which states: For
the Web Agent to operate to
Your httpd error log clearly indicates that you are trying to send a request
over SSL to a server which is not SSL enabled. Make sure that you have loaded
mod_ssl. If you are using an Apache source or binary distribution retrieved
from apache.org, make sure Apache is started with startssl as
No - that's not possible.
What you can do however, is to use mod_rewrite to retrieve the ssl id from the
client-rproxy connection and insert it as a header into the rproxy-balancer
connection. Search for previous threads on this list about forwarding client
certificate data to a backend server
That piece of shit has made me tear all of my hair out, but if you really have
to use it, please make yourself a favor and use the latest and greatest (SMWA
5QMR8). I think I counted something like 160 bug fixes in that release, as
compared to appx. 40 in other releases. Given all the problems
SetOutputFilter works very well, even in Location filters. There are lots of
happy customers of this feature, using it for such things as for example
compression of response bodies.
Are you quite sure your filter is NOT invoked? Could you possibly have it
generate some output to stderr?
I
SetOutputFilter works very well, even in Location filters. There are lots of
happy customers of this feature, using it for such things as for example
compression of response bodies.
Are you quite sure your filter is NOT invoked? Could you possibly have it
generate some output to stderr?
I
SetOutputFilter works very well, even in Location filters. There are lots of
happy customers of this feature, using it for such things as for example
compression of response bodies.
Are you quite sure your filter is NOT invoked? Could you possibly have it
generate some output to stderr?
I
You need to uncomment SSLEngine on in conf/extra/httpd-ssl.conf.
SSLProxyEngine is used to activate SSL to the backend server only.
The errors you get (Invalid method in request) are typical of a non-SSL server
receiving an unexpected SSL handshake.
-ascs
You are right. It does do port checks. Too bad it cannot determine that the
application server is unavailable based on the HTTP 502 the reverse proxy would
return in that case, and take the server off the list... Did you actually
verify that?
Truly, we abandoned using WebSphere and WebLogic
What I did notice though, is that replacing the %2F with / did work. What's the
story about this %2F ?
Unfortunately I'll have to pass on this one. If no-one else replies, you could
do a test using Apache 2.2.2, and possibly file a bug report. You may have more
luck filing a bug report after
Sorry; I did not really get it the first time around. The reverse proxy is
located between the plugin and WAS.
However I do not see why this should interfere with the work of the WAS plugin
since the latter, as far as I recall, basically just performs routing based on
the contents of the
Here you go:
RewriteRule ^/seach/(.*) /myscript.php/$1
RewriteRule ^/myscript.php/([a-z])([0-9]+)/(.*) /myscript.php/$3?param_$1=$2
[QSA,N]
RewriteRule ^/myscript.php/([a-z])([0-9]+)$ /myscript.php?param_$1=$2 [QSA,L]
-ascs
-Original Message-
From: news [mailto:[EMAIL PROTECTED] On
Good job. This suddenly rang a bell.
Check Bugzilla PR 15207 and upgrade to Apache 2.0.58 (or at least some version
= 2.0.55)
-ascs
-Original Message-
From: Markus Stockhausen [mailto:[EMAIL PROTECTED]
Sent: Wednesday, June 14, 2006 8:59 PM
To: Axel-Stéphane SMORGRAV; users
I thought there was a flag blocking URL escaping in rewrite rules, but I am
actually unable to find it in the module documentation. Checking the code,
however, I found the following:
bash-2.03$ grep -n NOESCAPE mod_rewrite.h
125:#define RULEFLAG_NOESCAPE 113
128:#define
); this flag prevents this from happening. This allows
percent symbols to appear in the output, as in
RewriteRule /foo/(.*) /bar?arg=P1\%3d$1 [R,NE]
which would turn '/foo/zed' into a safe request for '/bar?arg=P1=zed'.
-ascs
-Original Message-
From: Axel-Stéphane SMORGRAV
Sent: Tuesday, June
-Original Message-
From: Axel-Stéphane SMORGRAV
Sent: Thursday, June 08, 2006 3:41 PM
To: 'sarvothaman vittal'
Subject: RE: [EMAIL PROTECTED] Regarding Apache Plugin for weblogic server
There we go. The plugin is not compatible with 2.2.0. I do not know whether BEA
does supply
-Original Message-
From: Axel-Stéphane SMORGRAV
Sent: Thursday, June 08, 2006 4:05 PM
To: 'sarvothaman vittal'
Subject: RE: [EMAIL PROTECTED] Regarding Apache Plugin for weblogic server
Chances are that BEA does not currently support Apache 2.2.
Apache 2.2 is not binary compatible
What do you get when you execute
file /etc/httpd/modules/mod_wl_20.so ??
-ascs
From: sarvothaman vittal [mailto:[EMAIL PROTECTED]
Sent: Wednesday, June 07, 2006 9:43 PM
To: users@httpd.apache.org; [EMAIL PROTECTED]; [EMAIL PROTECTED]
Subject: [EMAIL
Are you using mod_ssl ? IN that case what is the value of the SSLMutex property
?
-ascs
-Original Message-
From: Steely, Bruce (Mission Systems) [mailto:[EMAIL PROTECTED]
Sent: Thursday, June 08, 2006 1:07 PM
To: users@httpd.apache.org
Subject: [EMAIL PROTECTED] Invalid argument:
I have had this kind of problems before, and I seem to remember I even posted a
bug about it.
For your information the error message you get does come from mod_ssl:
bash-2.03$ find . -type f -name \*.c -exec grep -l 'Failed to acquire global
mutex lock' {} \;
./modules/ssl/ssl_engine_mutex.c
I see you are using Apache 2.0.46. I seem to remember that there once was a bug
in mod_cache causing stale entries not to be replaced in certain versions of
Apache 2.0. Apache 2.0.46 may be one of the versions affected by this problem.
That would cause the cache provider to decline to serve the
This is definitely not the same problem.
First of all the problem was fixed in 2.2.1 and the original poster reports
using 2.2.2.
Second, I do not see any mention of caching the response under the key
http://_default_:80/ like in your case.
Frankly, I do not see anything indicating the
Well, the second response is definitively not served from cache (nor the first
one for that matter). The cache provider definitively tries to store the
response (measning that there is nothing in the headers preventing the response
from being cached) in both cases and declines to serve the
PROTECTED] mod_rewrite
Axel-Stéphane SMORGRAV wrote:
Rules below would be tested, but they wouldn't match unless the pattern
starts with scheme + :// + url-path.
unless the RewriteCond pattern starts with /. The above matches just fine.
I meant this hypothetical case
RewriteRule ^/a /b [R
It is really hard to understand exactly what your problem is because your
description is so sketchy. My understanding is that when you request
http://pippo/ntop/showPlugins.html?icmpWatch, the backend server issues a
redirect to http://localhost:3000/plugins/icmpWatch which you expect the
Seems almost right to me. If you want the querystring appended, you need to use
the QSA option. The L is not necessary since the redirect is immediate.
RewriteRule ^/directoryone/directorytwo/(mypage\.php)$ /$1 [R=301,QSA]
-ascs
-Original Message-
From: Robert Ionescu [mailto:[EMAIL
Your statement is wrong. The saves $2 and $3 are definitely known at that stage
of the rewriting process. The RewriteRule pattern is the first to be evaluated.
Check the mod_rewrite manual page. You can also test it for yourself with
RewriteLogLevel 3
-ascs
-Original Message-
From:
To: users@httpd.apache.org
Subject: Re: [EMAIL PROTECTED] mod_rewrite
Axel-Stéphane SMORGRAV wrote:
The L is not necessary since the redirect is immediate.
Rules below would be tested, but they wouldn't match unless the pattern starts
with scheme + :// + url-path.
Only other status codes than 301
Could you give some explanations wrt. your RewriteCond ? I have never seen
this kind of expressions before.
-ascs
-Original Message-
From: Robert Ionescu [mailto:[EMAIL PROTECTED]
Sent: Monday, May 29, 2006 7:55 PM
To: users@httpd.apache.org
Subject: Re: [EMAIL PROTECTED] rewrite rule
There must be something more to this, because there is no reason why the user
agent should encode differently depending on the server to which the request is
sent. At the time the request is sent, the browser does not even know what kind
of server it is sending the request to, and reverse
Although you do not specify which version of Apache you are using, I assume
that you are using 2.0.55 or newer.
AFAIK this problem does not exist in Apache 2.0.54 (or at least I have not
experienced it) with which I use rewrite rules quite extensively. Therefore I
think that you could replace
directives:
ProxyPass /path/to/exception !
-ascs
-Original Message-
From: Avraham Shapiro [mailto:[EMAIL PROTECTED]
Sent: Thursday, May 18, 2006 10:05 PM
To: Axel-Stéphane SMORGRAV; users@httpd.apache.org
Subject: RE: [EMAIL PROTECTED] ProxyPassReverse on Windows
Importance: Low
** Low
Replace
ProxyPass http://tswwma.lib.loc.gov/ http://192.168.0.2/
ProxyPassReverse http://tswwma.lib.loc.gov/ http://192.168.0.2/
with
ProxyPass/ http://192.168.0.2/
ProxyPassReverse / http://192.168.0.2/
-ascs
-Original Message-
From: Avraham
Would you by any chance be using mod_rewrite ??
-ascs
-Original Message-
From: Kjell Eidem [mailto:[EMAIL PROTECTED]
Sent: Thursday, May 18, 2006 12:10 PM
To: users@httpd.apache.org
Subject: [EMAIL PROTECTED] Exceeded the limit of 10 subrequest nesting levels
...
Hi List.
The
18, 2006 1:17 PM
To: users@httpd.apache.org
Subject: Re: [EMAIL PROTECTED] Exceeded the limit of 10 subrequest nesting
levels ...
No, I do'nt think so.
Kjell
Axel-Stéphane SMORGRAV wrote:
Would you by any chance be using mod_rewrite ??
-ascs
] Exceeded the limit of 10 subrequest nesting
levels ...
Removing Indexes does not help either.
The debug messages just point to the actual directory.
So the needle is still not found .
Kjell
Axel-Stéphane SMORGRAV wrote:
It's a little like the famous needle in a haystack.
Does removing
ServerLimit is what you are looking for if you are using Apache 2.x
Otherwise (Apache 1.3), it is MaxChild.
-ascs
-Original Message-
From: Kaushal Shriyan [mailto:[EMAIL PROTECTED]
Sent: Tuesday, May 16, 2006 3:13 PM
To: users@httpd.apache.org
Subject: [EMAIL PROTECTED] Query
Hi
How
Remove the Indexes option from the list of Options for every Location/Directory
section of your configuration.
For example change:
Directory /
Options Indexes FollowSymlinks
Order Deny,Allow
Allow all
/Directory
to:
Directory /
Options FollowSymlinks
Order Deny,Allow
I assume that your problem is due to the fact that the Windows file names are
case insensitive, whereas filenames on Unices are case sensitive. In that case
I believe there is nothing much you can do other than correcting all the links
in the HTML code, unless you want to rewrite all URL paths
I know that there have been problems with KeepAlive and IE when using https,
but not between Apache and IIS.
Would you by any chance know what the IIS KeepAlive timeout is? Might it
possibly be shorter than the Apache KeepAliveTimeout ? Does this only happen on
long requests (timeout of the
And in addition to this, if you run the Apache servers on Solaris, you may turn
on NFS caching.
-ascs
-Original Message-
From: William A. Rowe, Jr. [mailto:[EMAIL PROTECTED]
Sent: Monday, May 15, 2006 11:19 PM
To: users@httpd.apache.org
Subject: Re: [EMAIL PROTECTED] Hosting off of
In that case my guess is that it is the application that generates erroneous
redirect URLs. Had tomcat generated the redirect URLs, theyr would have
contained the port number also, e.g. http://andy:8012/
Keep your configuration the way it is (ProxyPreserveHost Off) and add the
following to the
even http://andy/webapp) to your
configuration.
-ascs
-Original Message-
From: Bo Najdrovsky [mailto:[EMAIL PROTECTED]
Sent: Monday, May 15, 2006 5:26 PM
To: users@httpd.apache.org
Subject: Re: [EMAIL PROTECTED] https to http proxy with Apache
Axel-Stéphane SMORGRAV wrote:
In that case my
The error you are referring to is generated during the processing of the
backend server response. It may be due to the backend server closing the
connection, or the connection timing out.
The timeout is 5 minutes by default, so unless the request really takes that
long to process, I think it
I guess the response to the POST is a redirect (302) which is not rewritten by
any of the ProxyPassReverse directives. In that case the URL of the Location
header probably starts with http://andy:port/ instead of
https://my.reverse.proxy.com/
What you need to do is figure out exactly what the
Unless you are doing this in order to familiarise yourself with writing modules
for Apache 2.0, I strongly suggest you use a module that already exists and
that provides a lot more flexibility than you module does. That module happens
to be mod_rewrite (funny how often it saves the day!)
VPN/IPsec solutions might also be considered in order to restrict access from
the Internet to only those able to establish a secure session... That would
restrict the number of users who would be able to probe the webmail gizmo.
-ascs
-Original Message-
From: Boyle Owen [mailto:[EMAIL
, May 12, 2006 3:30 PM
To: users@httpd.apache.org
Subject: Re: [EMAIL PROTECTED] Proxy errors
Thanks for this - I've tried changing the timeout so I'll see what happens.
Is it possible to catch the error and display something nicer instead?
cheers
Matt
on 12/05/2006 10:27 Axel-Stéphane SMORGRAV
Given the e-mail address of the original poster, I assume he is setting up an
Apache server in a professional context, and I would be very much surprised if
the provider did any kind of filtering. Chances are that they are their own
provider anyway...
It is much more likely he needs to talk
I think this question would better be submitted to the developpers' list.
-ascs
-Original Message-
From: Okamoto Toshiaki [mailto:[EMAIL PROTECTED]
Sent: Wednesday, May 10, 2006 12:06 PM
To: users@httpd.apache.org
Subject: [EMAIL PROTECTED] [Question]error_log
Hi Alls:
I have two
From what I understand you proxy to an application that generates HTML or
other contents where there are absolute references to other resources on the
same server.
What you should convince your dev team about is to generate links that do not
contain scheme://server:port but only the url-path.
What do you expect Reference/Glossary should be rewritten to ?
As far as I can tell from your rewrite rules, Reference/Glossary and
Reference/Glossary/ should be rewritten into Reference/index.php?ref=Glossary.
If that is not the case, you should turn on the rewrite logs at a log level of
at
No need to reinstall Apache. This is only a configuration issue.
You need to tell Apache where to find the
- Server certificate
- Private key associated with the server certificate
- CA Certificate
From your httpd.conf file, you probably include a configuration file called
ssl.conf. This
The requests will actually be processed by the rules of the correct named
virtual host (according to the host header); the only problem is that the
certificate the server will use for authenticating to the client is the one
defined in the first of the virtual hosts. At the time of SSL session
Can you see any reason why it would be looking for Apache header files under
/tmp/httpd-2.0.55 ?? Did you by any chance at some point untar the Apache
distrib under /tmp, run the configure script and then copy /tmp/httpd-2.0.55 to
/export/home/netiq/sol ?
-ascs
Start by reading the mod_filter documentation.
-ascs
From: Tiago Semprebom [mailto:[EMAIL PROTECTED]
Sent: Wednesday, May 03, 2006 1:51 PM
To: users@httpd.apache.org
Subject: [EMAIL PROTECTED] Add new Handler/Filter in Apache 2.0
I need to insert a new
IETF RFC2616 (www.ietf.org)
-ascs
-Original Message-
From: Michael Conlen [mailto:[EMAIL PROTECTED]
Sent: Monday, May 01, 2006 5:19 PM
To: users@httpd.apache.org
Subject: [EMAIL PROTECTED] mod_cache
I'm considering using mod_cache for a server but I haven't seen any
documentation on
That's called reverse proxying. Have a look at mod_proxy.
-ascs
-Original Message-
From: Matthew Claridge [mailto:[EMAIL PROTECTED]
Sent: Tuesday, May 02, 2006 11:22 AM
To: users@httpd.apache.org
Subject: [EMAIL PROTECTED] Redirect question
Hi,
This might seem like a really stoopid
I had a similar problem when using both mod_mem_cache and mod_disk cache with
Apache 2.0.54. I ended up abandoning mod_mem_cache and never experienced the
problem again. I may even have posted a bug report... but back then mod_cache
did not get much TLD from developers who were, as I understand
There has previously been some discussion on this list about the virtues of
memory caching versus disk caching. As I recall nobody ever claimed to have
observed performance gains using mod_mem_cache. I have myself not bothered to
run any load tests in an attempt to measure the benefits of
What 'bout this?
RewriteRule ^/About/([^/]+)/?$ /About/index.php?bout=$1 [L]
RewriteCond $1 !=About
RewriteRule ^/([^/]+)/?$ /index.php?home=$1 [L]
-ascs
From: David Blomstrom [mailto:[EMAIL PROTECTED]
Sent: Wednesday, April 26, 2006 2:59 PM
To:
That does not sound right at all.
1. AddHandler adds a handler for processing URLs having a specific extension.
In the case of the type-map handler, the default is the .var extension.
2. Apache does not modify the httpd.conf file so it should not grow or change.
3. You can safely remove that
I am afraid that mod_rewrite will process the request *before* mod_vhost_alias.
Therefore, in order to achieve what you want, I think you will need to abandon
mod_vhost_alias and rely solely on mod_rewrite.
For the user directories, maybe:
RewriteMaplowercase int:tolower
RewriteCond
In your httpd.conf or ssl.conf, there probably is a directive called
SSLCipherSuite. If you add -SSLv2 to the end of your CipherSuite string, and
restart Apache, you will have disabled SSLv2.
You can check the exact ciphersuites corresponding to a particular string with
the openssl ciphers
I believe that Apache just reports the contents of the User-Agent HTTP header.
Whatever UA information you find in the logs is what IE sent.
-ascs
-Original Message-
From: Fink, Mike [mailto:[EMAIL PROTECTED]
Sent: Wednesday, April 19, 2006 8:52 PM
To: users@httpd.apache.org
Subject:
Uhu.
The one thing that slipped past all of us is that you are using Apache as a
forward proxy. In that case the browser will not establish an SSL connection to
the proxy, but will use the CONNECT method as opposed to GET/PUT/POST/HEAD. It
is the proxy that will establish an SSL connection
mod_rewrite is definitely not loaded. Are you sure that the config file you
posted is the one really loaded by your Apache server ?
Would it be possible that the administrator uses another configuration file ?
If you execute
ps -ef | grep httpd
can you make out if there is a -f option on the
That was my experience too.
Additional tests showed that IE handles compressed JS and CSS well provided the
compressed size exceeds a certain threshold ( 4 KB ). If you really want to
compress such contents, you can use mod_filter to apply the DEFLATE filter to
JS and CSS provided their sizes
Would you mind sharing your frustration about Squid with me off the list (since
it is not really relevant for this forum) ?
I have no practical experience with Apache 2.2.0, but I have been using the
cache module of Apache 2.0 extensively in a reverse-proxy configuration for a
couple of
I am not so sure they have made that many changes to the code. I think it is
mostly their own compilation of httpd (for support reasons), with maybe a few
patches applied and then they have thrown in their own module for doing load
balancing and session affinity on WebSphere application
This is very clear: There is no process listening on IP 172.21.72.117 port
7002. If there was supposed to be a WebLogic server listening there, it is
donw. Try port 7001 (I believe that is the default WebLogic port), or verify
your WebLogic configuration and modify the configuration of the BEA
You're going to p*** a lot of people off by using such flashy HTML in your
mails...
Anyway, why don't you just create one VH for port 443 and one for port 80 ??
VirtualHost *:443
SSLEngine On
[more SSL stuff not included]
ProxyPass / http://server.my.com/
ProxyPassReverse /
The directory layout stuff can be solved using a relatively simple rewrite rule:
RewriteEngine On
RewriteRule ^/([^/]+)/(.*) /home/$1/public-html/$2
You could even enhance it so that it does the rewrite only if the user home
directory actually exists:
RewriteEngine On
RewriteCond
Using a wildcard for the IP address is perfectly fine. The problem is as you
point out, the fact that the first virtual host is not the named one, and since
it is the first, all requests will be processed according to the rules within
that.
-ascs
From:
1 - 100 of 325 matches
Mail list logo
