On 11/24/09, Jack Bates wrote:
> * /foo/ to deliver /foo/index.html, or whatever it would naturally deliver
> * /foo to deliver /foo.html always
IIUC, your problem boils down to:
/.htaccess has your desired behavior
/foo/.htaccess has some undesired, incompatible catch-all behavior
Sounds lik
Have you had a look at ntlm auth
That is what I use.. and it works well.
I had to compile it myself though
AuthName "NTLM Authentication"
NTLMAuth on
NTLMAuthHelper "/usr/bin/ntlm_auth
--helper-protocol=squid-2.5-ntlmssp"
NT
Clearly, no one has any particularly helpful suggestions on what to do
differently.
Apache, even under relatively light load, swallowed up 700+MB over two days.
So the only path forward I can see is to restart apache fairly regularly and
delve in to switching to nginx.
Thanks to those of you w
Aruna Gummalla wrote:
client y is on the same host as apache.
only client x is on a different host.
it does not matter. The point is that Apache will forward a HTTP
*request* to the "client y", and expect it to act like a HTTP server.
Unless your "client y" is really a HTTP server, it will no
client y is on the same host as apache.
only client x is on a different host.
Thanks & Regards,
Aruna.
--- On Wed, 11/25/09, André Warnier wrote:
From: André Warnier
Subject: Re: [us...@httpd] ProxyPass - mod_proxy
To: users@httpd.apache.org
Date: Wednesday, November 25, 2009, 6:10 AM
Aruna
Aruna Gummalla wrote:
Hi,
I am trying to configure mod_proxy. I want Apache to be the proxy server.
There is a client x which talks to Apache and Apache in turn passes on this request to other client y.
Taking you by the letter, that is not really what mod_proxy is supposed
to help you with.
Hi,
I am trying to configure mod_proxy. I want Apache to be the proxy server.
There is a client x which talks to Apache and Apache in turn passes on this
request to other client y. The client y responds to Apache and in turn should
send the response to client x.
Suppose, client y runs on port 99
> Jack Bates wrote:
> > I'm struggling a bit with this mod_rewrite rule,
>
> I am a bit intimidated by your detailed explanation and the level of
> expertise required to fully understand your requirements, never mind
> finding a solution. But reading your post in diagonals gives me the
> feel
I have Apache 2.2.11 and a web server behind it (CherryPy).
When I upload a large file to the CherryPy server, I see the file in
/tmp/modrproxy.tmp.FOO
It uploads completely.
Then Apache returns a 502 error without ever hitting the backend (the
first line of code in the handler is to spit out a log
Jack Bates wrote:
I'm struggling a bit with this mod_rewrite rule,
I am a bit intimidated by your detailed explanation and the level of
expertise required to fully understand your requirements, never mind
finding a solution. But reading your post in diagonals gives me the
feeling that maybe t
I'm struggling a bit with this mod_rewrite rule,
RewriteEngine On
RewriteCond %{REQUEST_FILENAME}.html -f
RewriteRule . %{REQUEST_FILENAME}.html
My goal is, when someone requests http://example.com/.../foo, to respond
with "foo.html", if it exists
I originally tried doing this with MultiViews, b
On Tue, Nov 24, 2009 at 11:51 AM, Steven Backus
wrote:
> Our crack security team scanned my web server with QualysGuard
> Enterprise. It found a "Gneric Web Server Directory Traversal
> Vulnerability." I'm at a loss to fix this, httpd -v returns:
>
> Server version: Apache/2.2.3
> Server built:
On Tue, Nov 24, 2009 at 12:38 AM, Boyle Owen wrote:
>> -Original Message-
>> From: bearsfoot [mailto:adam.p.reyno...@gmail.com]
>> Sent: Tuesday, November 24, 2009 3:24 AM
>> To: users@httpd.apache.org
>> Subject: [us...@httpd] More RewriteRule issues ..
>>
>>
>> Hi,
>>
>> I have the follo
Florent Georges wrote:
Hi,
I am using a virtual box (Ubuntu server 9.10 with VMware Fusion)
to test a web server. No problem to install Apache on this
Ubuntu box, of course. And I can access the default page after
an install by using http://xxx.xxx.xx.xx/ in my browser (on the
host machine
Our crack security team scanned my web server with QualysGuard
Enterprise. It found a "Gneric Web Server Directory Traversal
Vulnerability." I'm at a loss to fix this, httpd -v returns:
Server version: Apache/2.2.3
Server built: Nov 10 2009 09:06:57
I'm on RHEL 5 with current patches. Can an
On Tuesday 24 November 2009 12:47:16 Onur Ağın wrote:
> Yes, the cookie is JSESSIONID,
> In the server response, Set-Cookie:JSESSIONID=x;path=xxx;
> I am using a tomcat 6.0 server.
The tomcat should reply:
Set-Cookie:JSESSIONID=x.TOMCAT1;path=xxx;
It lacks the . and the route to the t
> -Original Message-
> From: Emmanuel Bailleul [mailto:emmanuel.baill...@telindus.fr]
> Sent: Tuesday, 24 November, 2009 09:49
> To: users@httpd.apache.org
> Subject: RE: [us...@httpd] Testing virtual hosts on a virtual machine
>
>
> > -Message d'origine-
> > De : Florent Georg
> -Message d'origine-
> De : Florent Georges [mailto:darkman_s...@yahoo.fr]
> Envoyé : mardi 24 novembre 2009 18:39
> À : Apache HTTPD users list
> Objet : [us...@httpd] Testing virtual hosts on a virtual machine
>
> Hi,
>
> I am using a virtual box (Ubuntu server 9.10 with VMware Fu
On Tue, Nov 24, 2009 at 5:39 PM, Florent Georges wrote:
> Hi,
>
> I am using a virtual box (Ubuntu server 9.10 with VMware Fusion)
> to test a web server. No problem to install Apache on this
> Ubuntu box, of course. And I can access the default page after
> an install by using http://xxx.xxx.
Hi,
I am using a virtual box (Ubuntu server 9.10 with VMware Fusion)
to test a web server. No problem to install Apache on this
Ubuntu box, of course. And I can access the default page after
an install by using http://xxx.xxx.xx.xx/ in my browser (on the
host machine.)
But the web server
Yes, the cookie is JSESSIONID,
In the server response, Set-Cookie:JSESSIONID=x;path=xxx;
I am using a tomcat 6.0 server.
On Tue, Nov 24, 2009 at 2:39 PM, Boyle Owen wrote:
> Forget the failover thing - Let's get back to your original problem
> which is stickysession not working.
>
> Have you
Forget the failover thing - Let's get back to your original problem
which is stickysession not working.
Have you checked you have the session cookie in the request and that
it's called JSESSIONID?
Check http://httpd.apache.org/docs/2.2/mod/mod_proxy.html#proxypass for
details on how it is suppose
What if I have a session clustering mechanism which works asynchronously, so
if host A fails, then the sessions will be replicated to server B in several
seconds, and if the session is sticky and request is moved to B, only
request that will come on that second will fail. But if the load balancer i
> "The downside is that if the desired server is really down, the
request
> will eventually fail."
>
> I wouldn't want this, the reason why I am using a load balancer
is to have high availability,
> not just to balance a load.
>
> How can I overcome this?
>
Hi!
I posted this at "Nabble » Apache » Tomcat » Tomcat - User" aswell:
http://old.nabble.com/Tomcat-6-and-Apache2-VS-Tomcat-6-alone-td26493078.html
But I want some mixed input so I'll post it here aswell, so here goes.
Im pretty new to this but have 2 friends that help me out. Though one of my
"The downside is that if the desired server is really down, the request
will eventually fail."
I wouldn't want this, the reason why I am using a load balancer is to have
high availability, not just to balance a load.
How can I overcome this?
Aren't there any alternatives?
Also what does it mean
Try adding "nofailover=On" to the Proxy tag, ie
...
By default, if the desired balancer member is busy, the request will be
routed to another one, even if the stickysession doesn't match (this is
"failover"). To force apache to hold the request until the server is
free again, you need to switch
Hi,
With the configuration below, sticky sessions won't work...
I checked that both servers get the request with the same session IDs.
Any ideas?
# Proxy
ProxyRequests Off
Order deny,allow
Allow from all
BalancerMember http://10.xxx:7101
BalancerMember http://10.xxx:7102
ProxyPass
thanks a lot for your reply, it works now...
Tue, Nov 24, 2009 at 11:42 AM, Mark Watts wrote:
>
> Use a trailing / on the ProxyPass lines.
> Also, add a ProxyPassReverse line to match the ProxyPass ones.
>
>
> Mark.
>
> On Tue, 2009-11-24 at 11:27 +0200, Onur Ağın wrote:
> > Hi,
> >
> >
> > I ma
Use a trailing / on the ProxyPass lines.
Also, add a ProxyPassReverse line to match the ProxyPass ones.
Mark.
On Tue, 2009-11-24 at 11:27 +0200, Onur Ağın wrote:
> Hi,
>
>
> I managed to do it with VirtualHost, but it now only works for the
> root document.
> How can I make it work for root d
Hi,
I managed to do it with VirtualHost, but it now only works for the root
document.
How can I make it work for root document and all other documents ( /* )
Thanks.
BalancerMember http://10.xxx:7101
BalancerMember http://10.xxx:7102
BalancerMember http://10.xxx:7103
> -Original Message-
> From: bearsfoot [mailto:adam.p.reyno...@gmail.com]
> Sent: Tuesday, November 24, 2009 3:24 AM
> To: users@httpd.apache.org
> Subject: [us...@httpd] More RewriteRule issues ..
>
>
> Hi,
>
> I have the following rules in my .htaccess.
>
> RewriteRule products/(.*)/
32 matches
Mail list logo
