While I have no specific insight to your problem, you might want to do the following. Grab the latest version of Apache, and use the mod_proxy in that. You also might want to take a look at the patches that are lying around for mod_proxy, theres been a lot of work on it of late, but most of it's waiting around and being implemented in the 2.0 version. Also you may want to put this on the new-httpd list..., that's more so where it should be, and that's where all the other modproxy hackers hang out. In particular Chris Sail, and Graham are two folks that might be able to help you out. Chris is the old mod_proxy maintainer, and Graham has done EXTENSIVE work on mod_proxy. There is also Sam, but he's more involved with the port to 2.0. It sounds like a bug to me with the caching or something like that. (Well, not directly involved with the caching, but auxiliarly involved with the caching) Thanks, Shane. On Fri, May 05, 2000 at 03:24:40PM +0100, lists wrote: > I am having a tricky problem with a mod_perl backend and a vanilla proxying > front end > > I have set up: > > Apache 1.3.9 + Mod_perl 1.23 + Embperl 1.2.1 as a back-end server > > Apache 1.3.9 + mod_proxy as a front-end server. > > Occasionally the back-end server gets into a state where it returns empty > documents > to the front-end, and the front-end then returns a > > "502 Proxy Error - document has no data" error to the client. > > The only thing logged by the backend is a 200 result code with "-" for the > amount of data transferred. > > I am at a complete loss as to what is happening - server load is not > excessive, and > there are plenty of spare servers. The only thing I have noticed is this > happens semi-consistently > after a *large* file upload (from the client) through the proxy to the > back-end server. The upload is > handled by EmbPerl. > > Once the server is in this state, it will continue serving no-data pages at > apparently random intervals until > it is restarted. > > Any ideas/pointers would be much appreciated - I am stuck because the > back-end is not giving any > error messages - just a 200 code... > > > Thanks, > > Chris Allen > [EMAIL PROTECTED] >
