gt;>
>>>> I am using tomcat8 and would like to configure ip address
>>>> with subnet in RemoteAddrValve for IP whitelisting (Example:
>>>> 0.0.0.0/0). Can anyone help in how to configure subnet in
>>>> allow field.
>>>>
>
On 01.11.2018 13:34, Mark Thomas wrote:
On 01/11/2018 12:23, André Warnier (tomcat) wrote:
On 01.11.2018 12:35, Madhur Khurana wrote:
Hi,
I am using tomcat8 and would like to configure ip address with subnet
in RemoteAddrValve for IP whitelisting (Example: 0.0.0.0/0). Can
anyone help in how
On 01/11/2018 12:23, André Warnier (tomcat) wrote:
> On 01.11.2018 12:35, Madhur Khurana wrote:
>> Hi,
>>
>> I am using tomcat8 and would like to configure ip address with subnet
>> in RemoteAddrValve for IP whitelisting (Example: 0.0.0.0/0). Can
>> anyone help in
On 01.11.2018 12:35, Madhur Khurana wrote:
Hi,
I am using tomcat8 and would like to configure ip address with subnet in
RemoteAddrValve for IP whitelisting (Example: 0.0.0.0/0). Can anyone help in
how to configure subnet in allow field.
The page at http://tomcat.apache.org/tomcat-8.5-doc
Hi,
I am using tomcat8 and would like to configure ip address with subnet in
RemoteAddrValve for IP whitelisting (Example: 0.0.0.0/0). Can anyone help in
how to configure subnet in allow field.
Thanks,
Madhur
=
Please refer to http
Server
>> Server number: 7.0.26.0
>
> https://wiki.apache.org/tomcat/FAQ/Linux_Unix#Q5
>
>> JVM Version:1.7.0_72-b14
>>
>> After setting the RemoteAddrValve:
>
> Where? In your web app, or globally?
it's in the server.xml on the path:
Server/Service
VM Version:1.7.0_72-b14
>
> After setting the RemoteAddrValve:
Where? In your web app, or globally?
> allow="127\.0\.0\.1|85.25.XX.XX" deny=""/>
>
> Tomcat works but all resources will not be showed anymore.
What happens? Error 403, blank page, no con
Hi
i work on an ubuntu system:
OS Name:Linux
OS Version: 2.6.32-042stab094.7
Architecture: amd64
With tomcat Server
Server number: 7.0.26.0
JVM Version:1.7.0_72-b14
After setting the RemoteAddrValve:
Tomcat works but all resources will not be showed anymore
On Tue, Sep 2, 2014 at 5:21 PM, Daniel Mikusa wrote:
>
>
>
> I didn't try curl. I believe it should work, assuming you send the right
> nonce.
>
>
> Okay.
> > So in order to get a nonce in the URL, did you first log in?
>
>
> Yes, but that was just because it was the quickest way to get a nonc
On Tue, Sep 2, 2014 at 4:41 PM, Shanti Suresh wrote:
> Hi Dan,
>
>
> On Tue, Sep 2, 2014 at 12:19 PM, Daniel Mikusa wrote:
>
> >
> >
> > I tried adding this to my manager app and it was triggering a 403. A
> quick
> > investigation showed the 403 was coming from the CRF filter (i.e. 403
> with
Hi Dan,
On Tue, Sep 2, 2014 at 12:19 PM, Daniel Mikusa wrote:
>
>
> I tried adding this to my manager app and it was triggering a 403. A quick
> investigation showed the 403 was coming from the CRF filter (i.e. 403 with
> direct access, success with nonce in the URL). Maybe you're seeing the
On Tue, Sep 2, 2014 at 10:53 AM, Shanti Suresh wrote:
> Hi Dan,
>
>
> On Tue, Sep 2, 2014 at 7:50 AM, Daniel Mikusa wrote:
>
> >
> >
> >
> > So using a RemoteAddrValve will allow you to restrict access by IP
> address,
> > but the ma
Hi Dan,
On Tue, Sep 2, 2014 at 7:50 AM, Daniel Mikusa wrote:
>
>
>
> So using a RemoteAddrValve will allow you to restrict access by IP address,
> but the manager application is still configured to require authentication.
> See this note from the link I sent previously.
>
>
> >
> >
> http://tomcat.apache.org/tomcat-7.0-doc/manager-howto.html#Configuring_Manager_Application_Access
> >
> >
> I would like localhost to access the JMXProxy servlet without a password.
> And hence, I used the RemoteAddrValve in the manager-context
roxy servlet without a password.
And hence, I used the RemoteAddrValve in the manager-context within
"manager.xml" to configure access. This setup used to work in 7.0.23 with
just an IP address restriction and no password. I have a perl script that
periodically invokes JSPs within the
On Fri, Aug 29, 2014 at 12:15 PM, Shanti Suresh wrote:
> Greetings,
>
> I am running Tomcat 7.0.52.
>
> I am a bit unsure as to why localhost is being denied a JMXProxy servlet
> query with a 403. I tried using curl as:
>
> curl http://localhost:8090/manager/heapused.jsp
>
> I have CATALINA_HOME
Greetings,
I am running Tomcat 7.0.52.
I am a bit unsure as to why localhost is being denied a JMXProxy servlet
query with a 403. I tried using curl as:
curl http://localhost:8090/manager/heapused.jsp
I have CATALINA_HOME/conf/Catalina/localhost/manager.xml set as follows:
I have heapu
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Thomas,
On 3/8/12 4:47 AM, Thomas Scheer wrote:
> Is there a way to block whole countries (e.g. Sudan) by ip-ranges
> and/or CIDR data? (in regex it would be a mess of data)
My spidey sense it tingling. I swear we discussed this.
Aah, here it is:
ht
Thomas Scheer wrote:
Hi,
Is there a way to block whole countries (e.g. Sudan) by ip-ranges and/or CIDR
data? (in regex it would be a mess of data)
In CIDR Format:
# Country: SUDAN
# ISO Code: SD
# Total Networks: 19
# Total Subnets: 283,904
41.67.0.0/18
41.78.108.0/22
41.79.24.0/22
41.79.120.0/
Hi,
Is there a way to block whole countries (e.g. Sudan) by ip-ranges and/or CIDR
data? (in regex it would be a mess of data)
In CIDR Format:
# Country: SUDAN
# ISO Code: SD
# Total Networks: 19
# Total Subnets: 283,904
41.67.0.0/18
41.78.108.0/22
41.79.24.0/22
41.79.120.0/22
41.95.0.0/16
41.202.
Hi Chris,
but "allows" is part of RequestFilterValve.
Not in the current trunk. Your code expects the "allows" variable to
be of type String[], and no such variable exists in RequestFilterValve.
Right: the point of the RequestFilterValve is that you don't have to
override the process() meth
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Remon,
On 10/19/2011 12:23 PM, Remon Sadikni wrote:
> Hi Chris,
>>
>> If you overrode the process() method (and I'm sure you changed
>> other things, too, since the variable "allows" is not part of
>> RequestFilterValve), then you really aren't gett
Hi Chris,
If you overrode the process() method (and I'm sure you changed other
things, too, since the variable "allows" is not part of
RequestFilterValve), then you really aren't getting anything by
extending RequestFilterValve.
but "allows" is part of RequestFilterValve. I only extended this
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Remon,
On 10/19/2011 7:57 AM, Remon Sadikni wrote:
> I managed to get it working. If you are interested in my solution
> for Tomcat 6: I extended the Valve RequestFilterValve and overwrote
> the method process with this content:
>
> // Check the allo
Hi André, hi Christopher,
The use of HTTP BASIC authentication confuses things here because
of the credential transfer mechanism (HTTP headers). I suppose
you could write a Valve that sniffs the user's IP address and
then adds HTTP headers to the request for the "Authentication"
header to essent
Hi Christopher,
You
should probably extend ValveBase so you don't have to implement
all the silly management methods.
http://tomcat.apache.org/tomcat-7.0-doc/api/org/apache/catalina/valves/ValveBase.html
This
will let you implement only the important method: invoke().
ok, I will try
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
André,
On 9/27/2011 7:40 AM, André Warnier wrote:
> The reason why I was mentioning further complexity for the Valve
> solution, is that as far as I know, the HttpServletRequest object
> is "immutable" (iow read-only), as it is received.
For the mos
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Remon,
On 9/27/2011 5:14 AM, Remon Sadikni wrote:
> Hi André, hi Christopher,
>
> thanks for your answers.
>>
>> The use of HTTP BASIC authentication confuses things here because
>> of the credential transfer mechanism (HTTP headers). I suppose
>> y
Remon Sadikni wrote:
Hi André, hi Christopher,
thanks for your answers.
The use of HTTP BASIC authentication confuses things here because of
the credential transfer mechanism (HTTP headers). I suppose you could
write a Valve that sniffs the user's IP address and then adds HTTP
headers to the r
Hi André, hi Christopher,
thanks for your answers.
The use of HTTP BASIC authentication confuses things here because of
the credential transfer mechanism (HTTP headers). I suppose you could
write a Valve that sniffs the user's IP address and then adds HTTP
headers to the request for the "Authen
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
André,
On 9/26/2011 9:29 AM, André Warnier wrote:
> You may also want to have a look at SecurityFilter, which could
> well be an easier way for you
> (http://securityfilter.sourceforge.net/) I do not think that it has
> provisions for "automatically"
Remon Sadikni wrote:
Dear Tomcat developers and users,
I managed to restrict a web application by IP-adress with
RemoteAddrValve and to restrict another one by basic authentication. Now
I would like to restrict the same web application by both methods:
- If the user is inside a specific
Remon Sadikni wrote:
Dear Tomcat developers and users,
I managed to restrict a web application by IP-adress with
RemoteAddrValve and to restrict another one by basic authentication. Now
I would like to restrict the same web application by both methods:
- If the user is inside a specific
Dear Tomcat developers and users,
I managed to restrict a web application by IP-adress with
RemoteAddrValve and to restrict another one by basic authentication. Now
I would like to restrict the same web application by both methods:
- If the user is inside a specific network (e.g. 134.134
On Thu, Sep 15, 2011 at 14:54, André Warnier wrote:
[...]
>
> One difficulty with implementing an Apache httpd-like scheme is that, in
> httpd, the order of the allow/deny plays a big role, and preserving the
> order is generally more difficult in XML.
>
Which is why there is "Order" ;)
> But ma
2011/9/15 André Warnier :
> Konstantin Kolinko wrote:
>>
>> 2011/9/15 André Warnier :
>>>
>>> On the other hand, using a regexp provides for quite a bit of flexibility
>>> regarding ranges of addresses. You could use something like :
>>> "(127\\.0\\.0\\.1)|((0?:0?:0?:0?:0?:0?)?:0?:1)"
>>
>> Just 12
Francis GALIEGUE wrote:
On Thu, Sep 15, 2011 at 14:25, André Warnier wrote:
[...]
OK, I've found the bug...
I have added an access log valve and here is what I see in it:
[15/Sep/2011:11:59:14 +0200] 0:0:0:0:0:0:0:1 (132 msec/964 bytes) 403
GET //manager/text/list HTTP/1.0
That explains it.
Konstantin Kolinko wrote:
2011/9/15 André Warnier :
On the other hand, using a regexp provides for quite a bit of flexibility
regarding ranges of addresses. You could use something like :
"(127\\.0\\.0\\.1)|((0?:0?:0?:0?:0?:0?)?:0?:1)"
Just 127\.0\.0\.1
It is XML - no need to double the slashe
2011/9/15 André Warnier :
> On the other hand, using a regexp provides for quite a bit of flexibility
> regarding ranges of addresses. You could use something like :
> "(127\\.0\\.0\\.1)|((0?:0?:0?:0?:0?:0?)?:0?:1)"
Just 127\.0\.0\.1
It is XML - no need to double the slashes.
Best regards,
Konsta
On Thu, Sep 15, 2011 at 14:25, André Warnier wrote:
[...]
>>
>> OK, I've found the bug...
>>
>> I have added an access log valve and here is what I see in it:
>>
>> [15/Sep/2011:11:59:14 +0200] 0:0:0:0:0:0:0:1 (132 msec/964 bytes) 403
>> GET //manager/text/list HTTP/1.0
>>
>> That explains it. So,
Francis GALIEGUE wrote:
On Thu, Sep 15, 2011 at 10:06, Francis GALIEGUE wrote:
On Wed, Sep 14, 2011 at 20:49, Mark Eggers wrote:
[...]
I've not tried this in Tomcat, but here's a thought.
According to:
http://tomcat.apache.org/tomcat-7.0-doc/config/valve.html#Remote_Address_Filter
Tomcat
On Thu, Sep 15, 2011 at 10:26, Francis GALIEGUE wrote:
[...]
>
> I have added 0:0:0:0:0:0:0:1 as an alternative instead of ::1 and it
> does work...
>
Which makes me think: the documentation SHOULD specify that regexes in
the "allow" and "deny" parameters of the valve are ANCHORED.
That's a pity
On Thu, Sep 15, 2011 at 10:06, Francis GALIEGUE wrote:
> On Wed, Sep 14, 2011 at 20:49, Mark Eggers wrote:
> [...]
>>
>> I've not tried this in Tomcat, but here's a thought.
>>
>> According to:
>>
>> http://tomcat.apache.org/tomcat-7.0-doc/config/valve.html#Remote_Address_Filter
>>
>>
>> Tomcat u
On Wed, Sep 14, 2011 at 20:49, Mark Eggers wrote:
[...]
>
> I've not tried this in Tomcat, but here's a thought.
>
> According to:
>
> http://tomcat.apache.org/tomcat-7.0-doc/config/valve.html#Remote_Address_Filter
>
>
> Tomcat uses java.util.regex for pattern matching. This means that if you want
Mark Eggers wrote:
...
Try using "127\\.0\\.0\\.1|::1" and see if that fixes your problem.
Of course ! I missed that one.
I have no idea why it would work in previous versions (have not checked the
change log).
neither have I.
Francis GALIEGUE wrote:
On Wed, Sep 14, 2011 at 17:28, André Warnier wrote:
Francis GALIEGUE wrote:
[...]
[...]
Maybe try to modify that regexp somewhat, like to
allow="(127\.0\.0\.1)|(::1)"
or
allow="127\.0\.0\.1|\:\:1"
just in case the regexp library version changed, and it now interp
- Original Message -
> From: Francis GALIEGUE
> To: Tomcat Users List
> Cc:
> Sent: Wednesday, September 14, 2011 8:42 AM
> Subject: Re: tomcat 7.0.21: bug in RemoteAddrValve?
>
> On Wed, Sep 14, 2011 at 17:28, André Warnier wrote:
>&
On Wed, Sep 14, 2011 at 17:28, André Warnier wrote:
> Francis GALIEGUE wrote:
[...]
>> > allow="127\.0\.0\.1|::1"/>
[...]
>>
> Maybe try to modify that regexp somewhat, like to
> allow="(127\.0\.0\.1)|(::1)"
> or
> allow="127\.0\.0\.1|\:\:1"
> just in case the regexp library version chan
Francis GALIEGUE wrote:
Hello,
I have a base Tomcat install with only the manager webapp in it at
startup (I deploy other webapps using it in text mode) but since I
upgraded from 7.0.16 to 7.0.21, the manager no longer works with the
RemoteAddrValve.
The context.xml is:
This
Hello,
I have a base Tomcat install with only the manager webapp in it at
startup (I deploy other webapps using it in text mode) but since I
upgraded from 7.0.16 to 7.0.21, the manager no longer works with the
RemoteAddrValve.
The context.xml is:
This worked fine with 7.0.16
I looked at the javadocs for the RemoteAddrValve and they provided no
further clarity on the syntax issue.
You're right, my test case mistakenly returned a false positive, ".*" could
match anything its true and their is no "common sense" wildcard in the Java
Regex
André Warnier wrote:
[...]
To match any address starting with "192.168.", use
or (if you want to be really finicky about it)
What is not very clear in the on-line Tomcat documentation, is whether a
remote client address of 192.168.1.2 would be translated to the string
"192.168.1.2" by Tomca
> From: Jonathan Mast [mailto:jhmast.develo...@gmail.com]
> Subject: RemoteAddrValve syntax
>
> The Tomcat docs says it uses the java.util.regex package
But you apparently didn't read the doc for java.util.regex, which is not
anything like the wildcards you tried to use:
ht
Jonathan Mast wrote:
How do I specify wildcards in the RemoteAddrValue declaration?
The Tomcat docs says it uses the java.util.regex package, so i wrote a test
case like this:
String patternStr = "192.168.*.*";
String searchStr = "192.168.1.2";
Pattern p = Pattern.compi
How do I specify wildcards in the RemoteAddrValue declaration?
The Tomcat docs says it uses the java.util.regex package, so i wrote a test
case like this:
String patternStr = "192.168.*.*";
String searchStr = "192.168.1.2";
Pattern p = Pattern.compile(patternStr);
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ed,
On 3/5/2009 12:02 PM, Edward Song wrote:
> Regardless, I recently wrote a java filter to filter IP's at the application
> level, which replicates the valve functionality.
> http://j2eewebprogrammer.blogspot.com/2008/12/filtering-ip-traffic-using-j
I'm always a few days behind the thread, but wanted to share.
If I had only known that I can configure the Valve at the Context level
(from Chuck's prior email).
Regardless, I recently wrote a java filter to filter IP's at the application
level, which replicates the valve functionality.
http://j2
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Zak,
On 2/27/2009 9:28 PM, Zak Mc Kracken wrote:
> I'd like to filter incoming requests with this criterion:
>
> if it's www.somewhere.com -> OK
> else if it's 1.2.3.4 -> OK
> else -> KO
You could always use our favorite urlrewrite tool:
http://tuck
> From: Gregor Schneider [mailto:rc4...@googlemail.com]
> Subject: Re: RemoteAddrValve and RemoteHostValve
>
> I understood that there was one open issue that Zac
> needed to combine a hostname and IP-adress
Early in the thread, someone pointed out that there's never any nee
Hi Chuck,
On Mon, Mar 2, 2009 at 3:07 PM, Caldarale, Charles R
wrote:
> Since a working setup was already provided, why not just use that?
>
Ehem - was it? I understood that there was one open issue that Zac
needed to combine a hostname and IP-adress - which was not possible
since both RemoteAdr
> From: Gregor Schneider [mailto:rc4...@googlemail.com]
> Subject: Re: RemoteAddrValve and RemoteHostValve
>
> Have you ever thought about fronting Tomcat with Apache HTTPD, then
> connecting it via mod_jk?
Are you serious? You want to add complexity and overhead just to control
Thanks Gregor, that's very interesting for production environments. I'll
try it.
Cheers.
M.
Gregor Schneider wrote:
On Mon, Mar 2, 2009 at 11:25 AM, Zak Mc Kracken wrote:
Gregor Schneider wrote:
you've been asking the valve-stuff because you want to limit the
access to requests coming fro
On Mon, Mar 2, 2009 at 11:25 AM, Zak Mc Kracken wrote:
> Gregor Schneider wrote:
>>
>> you've been asking the valve-stuff because you want to limit the
>> access to requests coming from localhost only?
>
> Yep!
>
>> why then not make tomcat listen on localhost only? configuration for
>> that's a w
Gregor Schneider wrote:
you've been asking the valve-stuff because you want to limit the
access to requests coming from localhost only?
Yep!
why then not make tomcat listen on localhost only? configuration for
that's a walk in the park...
My Tomcat is serving a number of webapps, I want t
On Sun, Mar 1, 2009 at 6:05 PM, Zak Mc Kracken wrote:
>
> Yes, but localhost-only is simpler in my case.
>
ehem, still not sure if i got you right:
you've been asking the valve-stuff because you want to limit the
access to requests coming from localhost only?
why then not make tomcat listen on lo
Gregor wrote:
marc,
do i understand you correct that you only whant to accept requests from
"localhost"?
I have a Java web application that computes some data from an existing
Java-based infrastructure and output it as simple plain text. The output
is intended to be consumed by other PHP app
Thanks again.
André Warnier wrote:
It would in my view make a lot more sense to have a single Remote Access
Valve to which one could specify, in "allow" or "deny", a hostname
AND/OR an IP address expression. Like
deny=".*\.badguys.com,10\.20\.30\.0" />
That's how it works in Apache httpd, and
urns
out that they both return "0:0:0:0:0:0:0:1%0", so now everything
works with:
Moreover, André's reply is pretty convincing, although it seems to i
mply that RemoteHostValve should be avoided (isn't DNS reverse looku
p cached?) and cannot be chained with RemoteAd
nnot be chained with RemoteAddrValve.
This is nitpicking, but I don't think that they cannot be chained per
se. The problem in this case is to specify the attributes in a way that
makes sense, which in this case is rather difficult to say the least.
The problem is that each Valve operates indepen
#x27;t DNS reverse lookup
cached?) and cannot be chained with RemoteAddrValve. Of course one can
do what you suggests, although this is a bit impractical in large
networks where one wouldn't like to care about IP changes of symbolic
names. Worse, I don't see what I could do to grant
> From: André Warnier [mailto:a...@ice-sa.com]
> Subject: Re: RemoteAddrValve and RemoteHostValve
>
> What I'm getting at, is that if you want to accept requests from
> "www.somewhere.com"
It's not clear to me whether the OP wants to check the origin or the
de
Zak Mc Kracken wrote:
[...]
Let's try this another way.
You want to allow requests from either www.somewhere.com, or one or more
IP addresses, and block all the rest.
First, filtering requests on the base of a DNS hostname is "expensive" :
it forces Tomcat to do a reverse DNS lookup. That
Gregor Schneider wrote:
What in the documentation
(http://tomcat.apache.org/tomcat-6.0-doc/config/valve.html) is the
part you don't understand?
Thanks for replying. Maybe it's me, but what I gather from the
documentation is that it's not possible to combine the two filters as I
want, i.e.: tell
Gregor Schneider wrote:
What in the documentation
(http://tomcat.apache.org/tomcat-6.0-doc/config/valve.html) is the
part you don't understand?
Thanks for replying. Maybe it's me, but what I gather from the
documentation is that it's not possible to combine the two filters as I
want, i.e.: tel
What in the documentation
(http://tomcat.apache.org/tomcat-6.0-doc/config/valve.html) is the
part you don't understand?
Rgds
Gregor
--
just because your paranoid, doesn't mean they're not after you...
gpgp-fp: 79A84FA526807026795E4209D3B3FE028B3170B2
gpgp-key available @ http://pgpkeys.pca.dfn.d
On Feb 27, 2009, at 9:28 PM, Zak Mc Kracken wrote:
Hi all,
I'd like to filter incoming requests with this criterion:
if it's www.somewhere.com -> OK
else if it's 1.2.3.4 -> OK
else -> KO
Is it possible to do that by combining RemoteHostValve and
RemoteAddrValve? How?
Hi all,
I'd like to filter incoming requests with this criterion:
if it's www.somewhere.com -> OK
else if it's 1.2.3.4 -> OK
else -> KO
Is it possible to do that by combining RemoteHostValve and
RemoteAddrValve? How? I simply tried to write them one after another,
but
Christopher Schultz wrote:
[...]
I see that tuckey's urlrewrite library can probably do this for me
(redirect somewhere else if the address doesn't match), but it seems a
bit overkill.
I recommend though. The setup is very easy and flexible, and the author
claims it is very light-weight. I ha
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
All,
I'm looking for something like the RemoteAddrValve but that can be used
on a particular URL pattern. Basically, I have an administrative "health
check" URL that I'd like to hit, but only from approved clients. The
rest of th
Found the problem. The docBase path was wrong. The "server" node in the
file tree was a hangover from Tomcat 5.
Mark Leone wrote:
Is RemoteAddrValve broken in 6.0.16? I have the following in
"manager.xml", located at %catalina_home%\Conf\Catalina\Localhost
Is RemoteAddrValve broken in 6.0.16? I have the following in
"manager.xml", located at %catalina_home%\Conf\Catalina\Localhost.
allow="127\.0\.0\.\d"/>
I also tried allow="^127\.0\.0\.\d", but I saw a bug fix for 6.0.12 that
said it would work the w
no you're not dude! You've helped me a lot! I've told you so before!
-Original Message-
From: Christopher Schultz [mailto:[EMAIL PROTECTED]
Sent: Wednesday, November 28, 2007 4:11 PM
To: Tomcat Users List
Subject: Re: RemoteAddrValve
-BEGIN PGP SIGNED MESSAGE-
Ha
> From: Christopher Schultz [mailto:[EMAIL PROTECTED]
> Subject: Re: RemoteAddrValve
>
> I'm an idiot.
End of the month - time to reboot :-)
- Chuck
THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY
MATERIAL and is thus for use only by the intended
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Chuck,
Caldarale, Charles R wrote:
>> From: Christopher Schultz [mailto:[EMAIL PROTECTED]
>> Subject: Re: RemoteAddrValve
>>
>> Propes, Barry L wrote:
>>> probably that path attribute is wrong, correct? Not nee
oh so I did recall correctly! ; ) Thought I'd seen Chuck punch that through a
time or two. : )
-Original Message-
From: Caldarale, Charles R [mailto:[EMAIL PROTECTED]
Sent: Wednesday, November 28, 2007 11:48 AM
To: Tomcat Users List
Subject: RE: RemoteAddrValve
> From: Chr
> From: Niki Diulgerov [mailto:[EMAIL PROTECTED]
> Subject: Re: RemoteAddrValve
>
> if I remove the allow="192.9.202.231"/>
It's className, not classname. Case matters.
- Chuck
THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY
MATERI
Diulgerov
Network Administrator
E-mail: [EMAIL PROTECTED]
Telephone : +33 4 89 87 77 77
Fax : +33 4 89 87 77 00
Web: http://www.codix-france.com
Caldarale, Charles R wrote:
From: Christopher Schultz [mailto:[EMAIL PROTECTED]
Subject: Re: RemoteAddrValve
Propes, Barry L wrote:
prob
> From: Propes, Barry L [mailto:[EMAIL PROTECTED]
> Subject: RE: RemoteAddrValve
>
> hmmm...ok...what is the one that is forgone in that version?
> The docBase?
No, you were correct about the path attribute, and Chris was mistaken.
The docBase attribute is required since
: RemoteAddrValve
Propes, Barry L wrote:
probably that path attribute is wrong, correct? Not needed on 5x?
Yes, it's necessary, since the OP isn't dropping a WAR anywhere, but
installing a context.xml file.
Nope, the path attribute is not allowed, and must be removed. T
> From: Christopher Schultz [mailto:[EMAIL PROTECTED]
> Subject: Re: RemoteAddrValve
>
> Propes, Barry L wrote:
> > probably that path attribute is wrong, correct? Not needed on 5x?
>
> Yes, it's necessary, since the OP isn't dropping a WAR anywhere, but
>
hmmm...ok...what is the one that is forgone in that version? The docBase?
-Original Message-
From: Christopher Schultz [mailto:[EMAIL PROTECTED]
Sent: Wednesday, November 28, 2007 11:36 AM
To: Tomcat Users List
Subject: Re: RemoteAddrValve
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Barry,
Propes, Barry L wrote:
> probably that path attribute is wrong, correct? Not needed on 5x?
Yes, it's necessary, since the OP isn't dropping a WAR anywhere, but
installing a context.xml file.
- -chris
-BEGIN PGP SIGNATURE-
Version: Gn
CTED]
Sent: Wednesday, November 28, 2007 10:57 AM
To: Tomcat Users List
Subject: RemoteAddrValve
Hello there,
Using tomcat 5.5.25 + jdk1.5.0_13
By default /tomcat/conf/Catalina/localhost/manager.xml looks like
privileged="true" antiResourceLocking="fals
probably that path attribute is wrong, correct? Not needed on 5x?
-Original Message-
From: Niki Diulgerov [mailto:[EMAIL PROTECTED]
Sent: Wednesday, November 28, 2007 10:57 AM
To: Tomcat Users List
Subject: RemoteAddrValve
Hello there,
Using tomcat 5.5.25 + jdk1.5.0_13
By default
Hello there,
Using tomcat 5.5.25 + jdk1.5.0_13
By default /tomcat/conf/Catalina/localhost/manager.xml looks like
privileged="true" antiResourceLocking="false"
antiJARLocking="false">
I'm changing it to:
privileged="true" antiResourceLocking="false"
antiJARLoc
Any ideas?
Cheers,
Pete
-Ursprüngliche Nachricht-
Von: Caldarale, Charles R [mailto:[EMAIL PROTECTED]
Gesendet: Dienstag, 14. November 2006 16:16
An: Tomcat Users List
Betreff: RE: Problem with RemoteAddrValve in Context.xml
From: Peter Neu [mailto:[EMAIL PROTECTED]
heers,
Pete
> -Ursprüngliche Nachricht-
> Von: Caldarale, Charles R [mailto:[EMAIL PROTECTED]
> Gesendet: Dienstag, 14. November 2006 16:16
> An: Tomcat Users List
> Betreff: RE: Problem with RemoteAddrValve in Context.xml
>
> > From: Peter Neu [mailto:[EMAIL PROTEC
achricht-
> Von: David Smith [mailto:[EMAIL PROTECTED]
> Gesendet: Dienstag, 14. November 2006 15:51
> An: Tomcat Users List
> Betreff: Re: AW: Problem with RemoteAddrValve in Context.xml
>
> I suspect the context.xml file in META-INF isn't honored unless you
> deploy your
> From: David Smith [mailto:[EMAIL PROTECTED]
> Subject: Re: AW: Problem with RemoteAddrValve in Context.xml
>
> I suspect the context.xml file in META-INF isn't honored unless you
> deploy your webapp as a web archive file (.war).
Not true - META-INF/context.xml is used r
on the same level as WEB-INF
>
>Cheers,
>Pete
>
>
>
>>-Ursprüngliche Nachricht-
>>Von: Martin Gainty [mailto:[EMAIL PROTECTED]
>>Gesendet: Dienstag, 14. November 2006 15:29
>>An: Tomcat Users List
>>Betreff: Re: Problem with RemoteAddrValve in Conte
1 - 100 of 118 matches
Mail list logo
