httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Aram Mirzadeh <>
Subject WWW Form Bug Report: "Location direction causes fork-bomb" on Linux (fwd)
Date Fri, 13 Sep 1996 01:04:25 GMT

It's not a bug report, POST question.... actually I would like to hear the
answer as well. 

> From:
> To:
> Symptoms:
> --
> I have written a couple CGI programs (bulliten 
> board and blackjack game) which accept commands
> via a form POST and return a Location: directive
> which is supposed to instruct the browser to 
> reload the page. I do this because using this 
> method causes multiple reloads of the page to 
> occupy 1 entry in the URL list (which makes it 
> easy to get back to my home pages, and helps keep
> users from doing things like submitting messages 
> twice and changing what cards are delt).
> Under Netscape's server (at work, but I'm getting
> ready to introduce them to apache!) this works 
> flawlessly. Under Apache, if I construct a fully
> qualified URL, I get a "document moved" page. If
> I use a full relative path (SCRIPT_NAME) then the
> server spawns off several dozen zombie CGI 
> processes and eventually consumes 100% CPU. If I
> use just the script name itself, then I get the 
> proper response.
> I don't know if I am to blame, or if this is an 
> Apache problem. I suspect the latter at least 
> partually 'cuz being able to disable a machine
> via the web server is bad.
> Please take a moment to write a one or two word
> reply. If I need to start rewriting my CGI's to 
> not do the Location thing, I'd like to get started
> Thanks,
> Christopher Shaulis
> --
> Backtrace:
> --
> --


  What is comedy?  Comedy is the art of making people laugh without making
  them puke.
                -- Steve Martin

Aram Mirzadeh				     Apache httpd team member
	    PGP Key
           BE 49 9D F6 2A A7 22 FC  02 E9 1E 3D F7 0C 67 A0

View raw message