--------------070106020502080605070601
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Alvise Nicoletti wrote:
> Alvise Nicoletti wrote:
>> Alvise Nicoletti wrote:
>>> Eric Covener wrote:
>>>> On Wed, Jan 6, 2010 at 6:04 AM, Alvise Nicoletti
>>>> <lists [at] alvisenicoletti.com> wrote:
>>>>
>>>>> I would like to restrict access to everything-but-mywebsite like the
>>>>> example:
>>>>>
>>>>
>>>>
>>>>> <IfModule mod_proxy.c>
>>>>> ProxyRequests Off
>>>>> <Proxy *>
>>>>> AddDefaultCharset off
>>>>> Order deny,allow
>>>>> Deny from all
>>>>>
>>>>> Allow from www.TOMCATWEBSITE.com
>>>>> </Proxy>
>>>>> ProxyVia On
>>>>> </IfModule>
>>>>
>>>>
>>>> That restricts access "from" an [client] address, not access "to" a
>>>> backend [webserver] address.
>>>>
>>>> If you're running a reverse proxy only (ProxyRequests off), and you've
>>>> told it to connect to a specific backend via ProxyPass, I don't see
>>>> why you need furtherer configuration to restrict anything.
>>>>
>>>>
>>> mhh ...
>>>
>>> the point is that the original configuration in my webserver was:
>>> <IfModule mod_proxy.c>
>>> ProxyRequests Off
>>> <Proxy *>
>>> AddDefaultCharset off
>>> Order deny,allow
>>> Deny from all
>>> </Proxy>
>>> ProxyVia On
>>> </IfModule>
>>>
>>> And everthing was working, BUT, I had to remove everything to make
>>> the tomcat6-apache2 bridge work.
>>> Also, in the header of that file I found written:
>>> #turning ProxyRequests on and allowing proxying from all may
>>> allow
>>> #spammers to use your proxy to send email.
>>>
>>> So I guess this is not good:
>>> <IfModule mod_proxy.c>
>>> ProxyRequests Off
>>> <Proxy *>
>>> AddDefaultCharset off
>>> </Proxy>
>>> ProxyVia On
>>> </IfModule>
>>>
>>>
>>>
>>> Or is it ok?
>>
>
mhh ....
> Do you guy confirm that leaving a webserver with mod_proxy.c enabled
> but with no rules is a good thing?
>
> So I relax up a bit ...
And what is this?
Connection attempts using mod_proxy:
65.183.2.75 -> http://lti-mail01.ltinetworks.com:25
<http://lti-mail01.ltinetworks.com:25>: 1 Time(s)
--------------070106020502080605070601
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Alvise Nicoletti wrote:
<blockquote cite="mid:4B45B2B7.1080106 [at] alvisenicoletti.com" type="cite">
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
<title></title>
Alvise Nicoletti wrote:
<blockquote cite="mid:4B44FC69.5040803 [at] alvisenicoletti.com"
type="cite">
<meta content="text/html;charset=ISO-8859-1"
http-equiv="Content-Type">
<title></title>
Alvise Nicoletti wrote:
<blockquote cite="mid:4B447319.3060405 [at] alvisenicoletti.com"
type="cite">
<meta content="text/html;charset=ISO-8859-1"
http-equiv="Content-Type">
Eric Covener wrote:
<blockquote
cite="mid:1404e5911001060309k6db65edauf28a863480fdd068 [at] mail. gmail.com"
type="cite">
<pre wrap="">On Wed, Jan 6, 2010 at 6:04 AM, Alvise Nicoletti
<a moz-do-not-send="true" class="moz-txt-link-rfc2396E"
href="mailto:lists [at] alvisenicoletti.com"><lists [at] alvisenicoletti.com ></a> wrote:
</pre>
<blockquote type="cite">
<pre wrap="">I would like to restrict access to everything-but-mywebsite like the
example:
</pre>
</blockquote>
<pre wrap=""><!---->
</pre>
<blockquote type="cite">
<pre wrap=""><IfModule mod_proxy.c>
ProxyRequests Off
<Proxy *>
AddDefaultCharset off
Order deny,allow
Deny from all
Allow from <a moz-do-not-send="true"
class="moz-txt-link-abbreviated" href="http://www.TOMCATWEBSITE.com">www.TOMCATWEBSITE.com</a>
</Proxy>
ProxyVia On
</IfModule></pre>
</blockquote>
<pre wrap=""><!---->
That restricts access "from" an [client] address, not access "to" a
backend [webserver] address.
If you're running a reverse proxy only (ProxyRequests off), and you've
told it to connect to a specific backend via ProxyPass, I don't see
why you need furtherer configuration to restrict anything.
</pre>
</blockquote>
mhh ...<br>
<br>
the point is that the original configuration in my webserver was:<br>
<pre wrap=""><IfModule mod_proxy.c>
ProxyRequests Off
<Proxy *>
AddDefaultCharset off
Order deny,allow
Deny from all
</Proxy>
ProxyVia On
</IfModule></pre>
<br>
And everthing was working, BUT, I had to remove everything to make the
tomcat6-apache2 bridge work.<br>
Also, in the header of that file I found written:<br>
#turning ProxyRequests on and allowing proxying from all may
allow<br>
#spammers to use your proxy to send email.<br>
<br>
So I guess this is not good:<br>
<IfModule mod_proxy.c><br>
ProxyRequests Off<br>
<Proxy *><br>
AddDefaultCharset off<br>
</Proxy><br>
ProxyVia On<br>
</IfModule><br>
<br>
<br>
<br>
Or is it ok?<br>
</blockquote>
<br>
</blockquote>
<br>
</blockquote>
<br>
<br>
mhh ....<br>
<br>
<blockquote cite="mid:4B45B2B7.1080106 [at] alvisenicoletti.com" type="cite">Do
you guy confirm that leaving a webserver with mod_proxy.c enabled
but with no rules is a good thing?<br>
<br>
So I relax up a bit ...<br>
</blockquote>
<br>
And what is this?<br>
<br>
Connection attempts using mod_proxy:<br>
65.183.2.75 -> <a moz-do-not-send="true"
href="http://lti-mail01.ltinetworks.com:25" target="_blank">http://lti-mail01.ltinetworks.<wbr>com:25</a>:
1
Time(s)
<br>
<br>
</body>
</html>
--------------070106020502080605070601--
