On Mon, Sep 7, 2009 at 9:41 PM, Ali Jawad wrote:
> Hi
> I got the following network setup
>
> |---Server A
> Internet --load balancer---Server B
> |---Server C
>
> The load balancer will send the requests in round robin fashion, and
> the traffic will
From that output, I can see that you're using an old release. The
debian package has since been fixed to use *:80 instead of *.
In any case, please read:
http://wiki.apache.org/httpd/CouldNotBindToAddress
To resolve your second issue.
Frank.
RicardoCh wrote:
Well, first, I mean that now the
Well, first, I mean that now the apache2 is configured exactly like
describes this Debian page:
http://www.debian-administration.org/articles/412
Second, this is the output asked by Francois:
Linux:~# apache2ctl -S
VirtualHost configuration:
wildcard NameVirtualHosts and _default_ servers:
*:*
Hi
I got the following network setup
|---Server A
Internet --load balancer---Server B
|---Server C
The load balancer will send the requests in round robin fashion, and
the traffic will be secured using HTTPS. All servers will host one
site using A
Is there a way of forcing webbrowser to present a login popup every time
they enter a protected URL? Now I login once and until I delete my
cookies, I can go to the URL without having a username and password
filled out, even not having the 'remember password' option active.
Have search for sessio
Give us the output from apache2ctl -S instead.
Frank
On Mon, Sep 7, 2009 at 12:32 PM, RicardoCh wrote:
> I have a web-file-router-proxycache-firewall server (ALL ON THE SAME
> MACHINE) Debian Lenny Squid 2.7-Apache 2-Samba 3-iptables.
>
>
> I'm going more crazy that ever!!!
>
> The problem is Vir
I have a web-file-router-proxycache-firewall server (ALL ON THE SAME
MACHINE) Debian Lenny Squid 2.7-Apache 2-Samba 3-iptables.
I'm going more crazy that ever!!!
The problem is VirtualHost and the warnings like:
[warn] _default_ VirtualHost overlap on port 80, the first has precedence
[war
Hi all folks!
Its my first message to the mailing list, so excuse me if Im posting on
wrong place. I have worked with Apache since 4 years ago, almost always with
version 2.X. So I have a little experience with this great web Server.
Lately, Im introducing NAS tecnologies with free software
Wow, that was a fast answer :)
I tried it, and got "RewriteCond: bad flag delimiters" and 500 error.
Saw that there was an extra space in the "RewriteCond %{REQUEST_URI} !
\.(js|jpg)$" rule, so changed it to "RewriteCond %{REQUEST_URI}
!\.(js|jpg)$".
Got rid of the 500 error, but now the rule didn
--- On Mon, 9/7/09, Krist van Besien wrote:
> RewriteCond %{REMOTE_ADDR}
> !$1
> RewriteRule
> /(\d+\.\d+\.\d+\.\d+)_.*
> - [F]
>
Thank you very much. That seems to do the trick. I'll give that a go.
---
On Mon, Sep 7, 2009 at 8:08 AM, Lars wrote:
> Hello list!
>
> I know basic mod_rewrite, not much, but enough to create basic rules.
>
> Now I need to create a rule that can handle this situation:
> * Work under the root (/) folder
> * Don't do anything under the /secure/ folder
> * Don't do anyt
Hello list!
I know basic mod_rewrite, not much, but enough to create basic rules.
Now I need to create a rule that can handle this situation:
* Work under the root (/) folder
* Don't do anything under the /secure/ folder
* Don't do anything with *.js, *.jpg
* Rewrite everything else to index.
On Mon, Sep 7, 2009 at 1:15 PM, Markus Wolf wrote:
>
>
> --- On Mon, 9/7/09, Krist van Besien wrote:
>> What do you actually mean with the "referer IP address".
>
> Sorry, yes, it should have said REMOTE_IP.
You can do something like that with rewrite rules. however,
RewriteRules operate on URLs,
On Mon, Sep 7, 2009 at 1:15 PM, Markus Wolf wrote:
>
>
> --- On Mon, 9/7/09, Krist van Besien wrote:
>> What do you actually mean with the "referer IP address".
>
> Sorry, yes, it should have said REMOTE_IP.
>
>
>> Or maybe you want to restrict access based on client IP?
>> That is
>> something di
> > What do you actually mean with the "referer IP
> address".
>
> Sorry, yes, it should have said REMOTE_IP.
Uhm, REMOTE_ADDR. ;)
-
The official User-To-User support forum of the Apache HTTP Server Project.
See htt
--- On Mon, 9/7/09, Krist van Besien wrote:
> What do you actually mean with the "referer IP address".
Sorry, yes, it should have said REMOTE_IP.
> Or maybe you want to restrict access based on client IP?
> That is
> something different, however.
That's what I would like to do.
--
On Sun, Sep 6, 2009 at 4:54 PM, Markus Wolf wrote:
> I have directories that contain IP addresses.
>
> /171.35.110.12_some_characters
> /172.30.97.4_some_other_random_characters
>
> Now I would like to only allow access to a folder in .htaccess when the
> referer IP address matches the first part
17 matches
Mail list logo
