CGI Debugging

sbatchu wrote on Sat Nov  1 22:48:20 CET 2008:
Hello all. I have apache running locally at on port 80. All
my html and cgi-bin files are located at /var/www/html and /var/www/cgi-bin
In EPIC, I have my project folder set to /var/www. So it reads all my html
and cgi files fine. Question is, when I do CGI debugging, I would like to
be able to debug using rather than

Is this possible? If so, please give me some ideas on this.

I'm using the latest test version of EPIC on Fedora 9.

sbatchu wrote on Mon Nov 10 00:03:21 CET 2008:
Any ideas guys??

Please help!
jploski wrote on Mon Nov 10 00:20:52 CET 2008:
You could install Apache, make it listen on port 80 on and
use the ProxyPass and ProxyPassReverse directives to translate the requests
back and forth. But why?
sbatchu wrote on Mon Nov 10 05:41:10 CET 2008:
The reason why I would like to debug like that is because all my get and
post requests, css, and hyperlinks all point to
dmitry_katko wrote on Fri Dec  5 10:02:54 CET 2008:
I have similar problem - every time I launch CGI debug(or run), it goes
to http://localhost:500x/ (x every time changes) but Apache is configured
to listen to 80 port. And after starting that way script asks to be saved
on disk or to be ran with standart interpreter(I guess Apache dont know
about this launch and my script is treated as simple file). If I try simple
 http://localhost/ script normally executes. 
So can anybody help me with this?
jploski wrote on Fri Dec  5 10:16:55 CET 2008:
When debugging with EPIC, your Apache setup is irrelevant. EPIC uses an
internal web server, which runs on port 5004. If you get another port assigned
every time, most likely you have not terminated the previous debugging session
properly (you can do it from the Debug view).

The normal procedure for CGI debugging with EPIC is to create a single launch
configuration which points to some "initial" CGI script, for example a login
page of your web site. For a typical project which keeps CGI scripts under
cgi-bin, this launch configuration should look as shown below:

HTML Root Directory = /path/to/project
HTML Startup File = /path/to/project/cgi-bin/
CGI Root Directory = /path/to/project

Note that the CGI Root Directory is equal to the HTML Root Directory. This
should prevent CGI scripts from being offered for download instead of being

Once the debugging session is started and the web server at :5004 is running,
you can use it to debug any CGI script within the project. That is, you
don't need to start a new debugging session per script. Just point your
browser to the new script's location (eg. http://localhost:5004/cgi-bin/
dmitry_katko wrote on Fri Dec  5 13:39:19 CET 2008:
Thank you for fast reply. You helped me a lot!

Note: The above is an archived snapshot of a forum thread. Use the original thread at to post comments.