mod_proxy/3440: Frontpage fails to connect to Apache/Frontpage server via Apache/proxy

["Alfredo E.Cotroneo" <al...@nexus.org>]

>Number:         3440
>Category:       mod_proxy
>Synopsis:       Frontpage fails to connect to Apache/Frontpage server via Apache/proxy
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    apache
>State:          open
>Class:          sw-bug
>Submitter-Id:   apache
>Arrival-Date:   Sat Nov 21 08:10:01 PST 1998
>Last-Modified:
>Originator:     alfredo@nexus.org
>Organization:
apache
>Release:        Apache/1.3.3 (Unix) FrontPage/3.0.4.2
>Environment:
Linux goodboy 2.0.33 
gcc version 2.7.2.3 
Apache 1.3.3
mod_frontpage.c and Apache1.3.3 patch from :
http://www.rtr.com/fpsupport/downloadApache130.htm
(ftp://www.rtr.com/pub/apache130/fp-patch-apache_1.3.3.tar.Z)

>Description:
I am trying to connect via Frontpage to an Apache 1.3.3 server complied with mod_frontpage and mod_proxy, 
using a local Apache 1.3.3 server compiled with mod_proxy (only) as proxy :

Frontpage/98 gives the following error when enabling proxy :

from syslog :
Nov 20 15:36:36 goodboy Microsoft FrontPage Server Extensions: Errore #60003 Messaggio: Tentativo di es
guire l'interprete Smart HTML sulla pagina non in formato HTML "". (userid 923)
(Translates to : Error #60003 trying to execute Smart HTML interpreter on 
a non HTML page "" )

Frontpage works correclty when an Apache/frontpage proxy server is NOT selected 
or when I specify Netscape proxy server in Frontpage/98.

I noticed these two differences  in the log file, the first one is produced 
when connecting with no proxy enabled in Frontpage/98, the second three lines 
are produced with an Apache 1.3.3/proxy/with fronptage_mod  enabled in 
Frontpage/98.

In the access_log entry below please notice the last line :

"POST /_vti_bin/shtml.exe/_vti_rp HTTP/1.0"

should be :
"POST /_vti_bin/shtml.exe/_vti_rpc HTTP/1.0"

Maybe the URL is not passed correctly from the proxy module ?


Excerpt from access_log on the proxy server (compiled with mod_proxy and mod_frontpage) :

uni-port2-148 - - [21/Nov/1998:15:23:32 +0100] "POST /_vti_bin/shtml.exe/_vti_rpc HTTP/1.0" 200 227
uni-port2-148 - - [21/Nov/1998:15:23:32 +0100] "POST /_vti_bin/_vti_aut/author.exe HTTP/1.0" 401 401

With mod_frontpage.c and mod_proxy :
uni-port2-148 - - [21/Nov/1998:15:17:52 +0100] "GET /_vti_inf.html HTTP/1.0" 200 1716
uni-port2-148 - - [21/Nov/1998:15:17:53 +0100] "POST /_vti_bin/shtml.exe/_vti_rp HTTP/1.0" 200 175


The frontpage module/patch to Apache-1.3.3 was downloaded from :
ftp://www.rtr.com/pub/apache130/fp-patch-apache_1.3.3.tar.Z
(see http://www.rtr.com/fpsupport/downloadApache130.htm)

This behaviour appeared in version Apache-1.3.0 and above, it worked OK in 1.2.X.

If you need further details I will be glad to provide more information. 
With best regards,

Alfredo Cotroneo
(Milano, Italy)
>How-To-Repeat:
We need to enable proxy access to your client, please send e-mail with IP number 
or class C if you want to test. Our proxy is prox.nexus.org.
>Fix:
no
>Audit-Trail:
>Unformatted:
[In order for any reply to be added to the PR database, ]
[you need to include <ap...@Apache.Org> in the Cc line ]
[and leave the subject line UNCHANGED.  This is not done]
[automatically because of the potential for mail loops. ]
[If you do not include this Cc, your reply may be ig-   ]
[nored unless you are responding to an explicit request ]
[from a developer.                                      ]
[Reply only with text; DO NOT SEND ATTACHMENTS!         ]