Work at SourceForge, help us to make it a better place! We have an immediate need for a Support Technician in our San Francisco or Denver office.

Close

#7 cgi scripts only run under mod_perl

closed-wont-fix
nobody
Browsing (93)
5
2001-10-09
2001-05-30
Malcolm Box
No

There doesn't seem to be a good reason to require these
scripts to run under mod_perl only (although it has
obvious performance improvements). Not requiring
mod_perl would enable other webservers/platforms to be
used more easily

Discussion

  • Malcolm Box
    Malcolm Box
    2001-05-30

    Logged In: YES
    user_id=215386

    More investigation:

    Removing the print "HTTP/1.0 200 OK" line from printhttp (in
    Common.pm) allows the scripts to run under CGI without
    problems, but then running under Apache::Registry causes
    some HTTP headers to show up in the HTML.

    Probably the correct solution for CGI at the moment is to
    rename the scripts to nph-* so that they can issue the HTTP
    headers directly (as they do under Apache::Registry).
    Currently I can find no way to switch mod_cgi into nph mode
    for all/selected files.

     
  • Malcolm Box
    Malcolm Box
    2001-05-30

    Logged In: YES
    user_id=215386

    Moving this to later unless anyone is really bothered by
    having to have mod_perl.

     
  • Malcolm Box
    Malcolm Box
    2001-05-30

    • status: open --> open-later
     
  • Malcolm Box
    Malcolm Box
    2001-08-04

    • assigned_to: mbox --> nobody
     
  • Malcolm Box
    Malcolm Box
    2001-10-09

    • status: open-later --> closed-wont-fix
     
  • Malcolm Box
    Malcolm Box
    2001-10-09

    Logged In: YES
    user_id=215386

    The workaround suggested below will work for those that
    care, and it's not worth renaming everything in the main tree.

     
  • Logged In: YES
    user_id=308126

    Well, there's one more thing which would better done in
    separated processed (than in this wuss of mod_perl scripts).
    For example, I think quite some of my "lib not found"
    problems wouldn't occure in running separately. These errors
    tend to resolve when I request the page as often as needed
    to get the initial apache worker process...