On Tue, 12 Mar 2002 17:42:22 -0500
Pierre Fortin <[EMAIL PROTECTED]> wrote:

> On Tue, 12 Mar 2002 13:33:00 -0600 "J. Craig Woods" <[EMAIL PROTECTED]>
> wrote:
> 
> > James wrote:
> > > 
> > > > On Sun, 2002-03-10 at 20:26, Pierre Fortin wrote:
> > > > > Ooops...  forgot to add that I needed to hit Return after sending
> > > > > the GET; so the full instructions are:
> > > > >
> > > > >    telnet <server> 80
> > > > >    GET http://<some_other_server> HTTP/1.0
> > > > >    <Return>
> > > > >
> > > > > Without the extra return, the command "just sits" there as you
> > > > > discovered.
> > > > >
> > > > > Sorry for the oversight,
> > > > > Pierre
> > > > >
> > > > > On Sun, 10 Mar 2002 18:01:13 -0700 Ken Thompson <[EMAIL PROTECTED]>
> > > > > wrote:
> > > >
> > > > Pierre,
> > > >
> > > > Thankfully mine said connection refused.
> > > 
> > > Mine 3 simply gave me the index.html page from the box I originally
> > > telneted into. Not from another server.
> > > 
> > > James
> > > 
> > 
> > Just to save my sanity, what is the expected response from a telnet
> > session into your web server's port? Like James, I get back my
> > index.html when I run the "GET blah..blah..". Does someone know of some
> > *good* documentation about this particular aspect of running a apache
> > web sever? I have looked but found little on this topic
> > (hint..hint..Pierre)
> 
> Let's not forget the reason I posted this...  if your web server accepts
> the above command and serves a remote page, then it can be used by kiddies
> to get access to servers while making it seem all those requests are
> really coming from you.  This is due to your server "proxying"...
> 
> Give me your server and I'll see if I can use it to access other sites
> through it...  :^)
> 
> Here's an example of the problem where I connect to Mandrake and actually
> get a Cisco page:
> 
> $ telnet www.mandrakesoft.com 80
> Trying 63.209.80.236...
> Connected to www.mandrakesoft.com (63.209.80.236).
> Escape character is '^]'.
> get http://www.cisco.com HTTP/1.0
> 
> HTTP/1.0 200 OK
> Date: Tue, 12 Mar 2002 22:37:21 GMT
> Server: Apache/1.3.12 (Unix)
> Content-Type: text/html
> 
> <HTML>
> <HEAD>
> [snipped much META stuff]
> 
> <TITLE>Cisco Connection Online by Cisco Systems, Inc.</TITLE>
> 
> [snipped rest of page]
> 
> 
> Turn off proxy in server to stop this...
> 
> Pierre
> 

Pierre,
  I never doubted you.  Just wondering how it was supposed to work .... when it's bad 
that is.  To clear up turning off proxy, are you refering to removing the following 
line from httpd.conf?

LoadModule proxy_module       modules/libproxy.so
&
AddModule mod_proxy.c


Along with commenting out 

### IP Address/Port and Proxied configuration section
###
# The APACHEPROXIED setting can be set in /etc/rc.d/init.d/httpd if you
# are using a proxy or accelerator, like the Apache-SGI or khttpd, so that
# the fast web server serves static content while Apache handles the 
# cgi or php files

#BindAddress *
<IfDefine !APACHEPROXIED>
    Port 80
    Listen 80
</IfDefine>
<IfDefine APACHEPROXIED>
    Port 8080
    Listen 8080
</IfDefine>

# Likewise, we can set apache as the server by default and send perl
# requests via ProxyPass to apache-mod_perl. It increases performance
# since the perl interpreter is only used for perl and the standard apache
# does all the html and image files, with a smaller footprint.
# Likewise, we can set apache as the server by default and send perl
# requests via ProxyPass to apache-mod_perl. It increases performance
# since the perl interpreter is only used for perl and the standard apache
# does all the html and image files, with a smaller footprint.
#
# If you install apache and apache-mod_perl, this is the default config.
# If you don't want two web servers to use perl, uninstall apache, and
# apache-mod_perl will not be proxied.

<IfDefine PERLPROXIED>
    RewriteEngine on
    RewriteRule ^proxy:.*  -  [F]
    RewriteRule ^(.*\/perl\/.*)$  http://%{HTTP_HOST}:8200$1 [P]
    RewriteRule ^(.*\/cgi-perl\/.*)$  http://%{HTTP_HOST}:8200$1 [P]
</IfDefine>


If so have you tried this on port 8080 as well? My attempt to try it on 
mandrakesoft.com site just hung with no telnet established.  I'm also curious if it's 
a perl thing or an apache thing that causes the problem.  Since it seems that both can 
do the proxies. (seems to open up 8200 for perl but maybe I'm wrong.)

James

> 
> 

Want to buy your Pack or Services from MandrakeSoft? 
Go to http://www.mandrakestore.com

Reply via email to