You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@httpd.apache.org by System Owner <ro...@en3.engelschall.de> on 1998/03/21 12:32:13 UTC

Proxy module deficiency list: Please help!

I want at least create a list of currently known and existing deficiencies of
the proxy module. My idea is that when we have this list we can at least fix
some of these deficiencies for 1.3. So, please complete the following list
with as much detailed information as you know:

 Current deficiencies of mod_proxy:
 ----------------------------------
  o missing HTTP/1.1 conformity, especially:
      - support for KeepAlives
      - ??
  o some reported segmentation faults
    (see: query-pr -i --state="open|analyzed|suspended|feedback" 
                   --category="mod[ _]proxy")
  o support for proxy authentication
  o ??

                                       Ralf S. Engelschall
                                       rse@engelschall.com
                                       www.engelschall.com

Re: Proxy module deficiency list: Please help!

Posted by Rodent of Unusual Size <Ke...@Golux.Com>.
System Owner wrote:
> 
> I want at least create a list of currently known and existing deficiencies of
> the proxy module. My idea is that when we have this list we can at least fix
> some of these deficiencies for 1.3. So, please complete the following list
> with as much detailed information as you know:

How about addressing [some of] the open PRs as a start?  From the bugdb:

 314 Truncated (short/invalid) files are proxy-cached. Ought to be
invalidated. 
 362 Mod_proxy doesn't allow change of error pages 
 440 Proxy doesn't deliver documents if not connected 
 505 proxy ftp does not work with anonftpd server by D. J. Bernstein 
 534 proxy converts ~name to %7Ename when name starts with a dot (.) 
 612 Proxy FTP Authentication Fails 
 668 Two problems with user:password@host URLs 
 671 server access restrictions apply to proxy requests 
 700 Proxy doesn't do links right for OpenVMS files through ftp: 
 747 Proxy caches documents even if transmission was interrupted 
 890 Proxy doesn't work offline if I reload the document 
 980 Controlling Access to Remote Proxies would be nice... 
 994 Adding authentication "on the fly" through the proxy module 
1085 ProxyRemote make a dead cycle. 
1166 ``nph-'' not honored (no buffering) for ProxyRemote mapping 
1230 Page underlined input fields are missing for
http://catalogue.spotimage.fr:8001/ 
1290 Need to know "hit-rate" on proxy cache 
1307 Cache growing and staying above the set size (CacheSize) 
1326 HTTPS - Cannot Connect! (PR#1024, PR#1105) 
1349 Proxy server stops working when there is no route to host 
1415 POSTs with Content-Length: header have any trailing CRLF stripped from
body 
1472 extra headers on POST method CGI returns 
1532 Proxy transfer logging       
1547 No HTTP_X_FORWARDED_FOR set... 
1565 ftp proxy grabs files relative to login point, which may cause some
confusion 
1567 ProxyRemote proxy requests fail authentication by firewall 
1573 SIGSEGV in proxy module observed with CONNECT request (https) 
1583 Error in netscapehost.patch  
1606 ProxyPass ain't useful; but it could be if a ProxyFilter directive were
added 
1635 ProxyPass doesn't serve files with extensions  some confusionctive were
added 
1702 mod_proxy to support persistent conns? nsions
1785 Proxy-Authenticate code in http_protocol fails with ProxyPass and
Netscape 
1805 Proxy would not access another Apache server on the same host, trying to
access itself1805
1810 NoProxy doesn't work on Non-Standard Ports... 
1878 listing of proxy cache content 
1942 CONNECT Problem with SSL Proxy 

#ken	P-)}

Ken Coar                    <http://Web.Golux.Com/coar/>
Apache Group member         <http://www.apache.org/>
"Apache Server for Dummies" <http://WWW.Dummies.Com/

Re: Proxy module deficiency list: Please help!

Posted by Martin Kraemer <Ma...@mch.sni.de>.
On Wed, Mar 25, 1998 at 11:23:37AM -0700, Marc Slemko wrote:
> On Wed, 25 Mar 1998, Dean Gaudet wrote:
> > > 	Content-Encoding: x-gzip
> > > ---->>>>                  ^^^^^^Bogus.
> > 
> > What's bogus about this?

Yeah, Dean is right: Because I issued a HEAD request, RFC2068 explicitely
states that header lines like Content-Length etc. represent the
document's attributes, and Content-Length for example may show a non-
zero size even though no body is allowed in the reply.

The error is therefore not the fact that we see a (guessed) value of
"Content-Encoding: x-gzip" here, but that there's a body even though it
was a HEAD request (clearly a proxy error). As per RFC2068:

   Except when responding to a HEAD request, the
   server SHOULD include an entity containing an explanation of the
   error situation, ...
> 
> ... But
> not only does that error have a body, it also claims that the body is
> gzipped HTML.

Yeah, that was what struck me.

    Martin
-- 
| S I E M E N S |  <Ma...@mch.sni.de>  |      Siemens Nixdorf
| ------------- |   Voice: +49-89-636-46021     |  Informationssysteme AG
| N I X D O R F |   FAX:   +49-89-636-44994     |   81730 Munich, Germany
~~~~~~~~~~~~~~~~My opinions only, of course; pgp key available on request

Re: Proxy module deficiency list: Please help!

Posted by Marc Slemko <ma...@worldgate.com>.
On Wed, 25 Mar 1998, Dean Gaudet wrote:

> 
> 
> On Wed, 25 Mar 1998, Martin Kraemer wrote:
> 
> > 	Content-Encoding: x-gzip
> > ---->>>>                  ^^^^^^Bogus.
> 
> What's bogus about this?
> 
> Dean
> 

Look at the context:

        HEAD ftp://some.server/pub/ls.gz

        HTTP/1.0 500 Proxy Error
        Date: Wed, 25 Mar 1998 16:58:26 GMT
        Server: Apache/1.3b6-dev BS2000-OSD/2.0A
        Connection: close
        Content-Type: text/html
        Content-Encoding: x-gzip
---->>>>                  ^^^^^^Bogus.

        <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
        <html><head><title>Proxy Error</title><head>
        <body><h1>Proxy Error</h1>
        The proxy server could not handle this request.
        <p>
            Reason: <b>Not logged in</b>

You do a HEAD, don't connect to the server, so you get an error back.  But
not only does that error have a body, it also claims that the body is
gzipped HTML.

I will ignore the "content-encoding is fscking useless because clients are
pathetic" part of it.


Re: Proxy module deficiency list: Please help!

Posted by Dean Gaudet <dg...@arctic.org>.

On Wed, 25 Mar 1998, Martin Kraemer wrote:

> 	Content-Encoding: x-gzip
> ---->>>>                  ^^^^^^Bogus.

What's bogus about this?

Dean


Re: Proxy module deficiency list: Please help!

Posted by Martin Kraemer <Ma...@mch.sni.de>.
On Sat, Mar 21, 1998 at 12:32:13PM +0100, System Owner wrote:
> 
> I want at least create a list of currently known and existing deficiencies of
> the proxy module.

o   Auto-Authentication for proxy ftp (when no username/password is
    supplied, but the ftp server neeeds one, reply with a 401 and retry
    when WWW-Auth is there.

o   Improve Content-Type detection of ftp proxy. Currently, the
    following severe deficiency (;-) can happen:
	HEAD ftp://some.server/pub/ls.gz

	HTTP/1.0 500 Proxy Error
	Date: Wed, 25 Mar 1998 16:58:26 GMT
	Server: Apache/1.3b6-dev BS2000-OSD/2.0A
	Connection: close
	Content-Type: text/html
	Content-Encoding: x-gzip
---->>>>                  ^^^^^^Bogus.

	<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
	<html><head><title>Proxy Error</title><head>
	<body><h1>Proxy Error</h1>
	The proxy server could not handle this request.
	<p>
	    Reason: <b>Not logged in</b>
    (When I do a HEAD, even for errors, may I ever get a body entity
    back? And the type is bogus, of course).

    But when access is possible and the file can be fetched, then this
    happens:
	HEAD ftp://some.server/pub/ls.gz

	HTTP/1.0 200 OK
	Content-Type: text/plain
	Content-Length: 14916
    No Body, okay. But no Content-Type either (and no Server:, Date: etc.)

    Martin
-- 
| S I E M E N S |  <Ma...@mch.sni.de>  |      Siemens Nixdorf
| ------------- |   Voice: +49-89-636-46021     |  Informationssysteme AG
| N I X D O R F |   FAX:   +49-89-636-44994     |   81730 Munich, Germany
~~~~~~~~~~~~~~~~My opinions only, of course; pgp key available on request

Re: Proxy module deficiency list: Please help!

Posted by Chuck Murcko <ch...@topsail.org>.
>From mod_proxy.h:

1. add 230 response output for ftp now that it works

2. Make the ftp proxy transparent, also same with (future) gopher & wais

3. Use protocol handler struct a la Apache module handlers (Dirk van
Gulik)

4. Use a cache expiry database for more efficient GC (Jeremy Wohl)

5. Bulletproof GC against SIGALRM

In addition, child process for GC would be a good thing.

System Owner wrote:
> 
> I want at least create a list of currently known and existing deficiencies of
> the proxy module. My idea is that when we have this list we can at least fix
> some of these deficiencies for 1.3. So, please complete the following list
> with as much detailed information as you know:
> 
>  Current deficiencies of mod_proxy:
>  ----------------------------------
>   o missing HTTP/1.1 conformity, especially:
>       - support for KeepAlives
>       - ??
>   o some reported segmentation faults
>     (see: query-pr -i --state="open|analyzed|suspended|feedback"
>                    --category="mod[ _]proxy")
>   o support for proxy authentication
>   o ??
> 
>                                        Ralf S. Engelschall
>                                        rse@engelschall.com
>                                        www.engelschall.com

-- 
chuck
Chuck Murcko            The Topsail Group             West Chester PA
USA
chuck@topsail.org

Re: Proxy module deficiency list: Please help!

Posted by Marc Slemko <ma...@worldgate.com>.
On Sat, 21 Mar 1998, System Owner wrote:

> 
> I want at least create a list of currently known and existing deficiencies of
> the proxy module. My idea is that when we have this list we can at least fix
> some of these deficiencies for 1.3. So, please complete the following list
> with as much detailed information as you know:
> 
>  Current deficiencies of mod_proxy:
>  ----------------------------------
>   o missing HTTP/1.1 conformity, especially:
>       - support for KeepAlives
>       - ??

and 1.1 caching semantics.

>   o some reported segmentation faults
>     (see: query-pr -i --state="open|analyzed|suspended|feedback" 
>                    --category="mod[ _]proxy")
>   o support for proxy authentication

Hmm?  What is wrong with proxy auth?


>   o ??
> 
>                                        Ralf S. Engelschall
>                                        rse@engelschall.com
>                                        www.engelschall.com
>