www-apache-bugdb mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "André" de Jesus <andre.je...@netc.pt>
Subject os-windows/7594: Apache + ActivePerl + Windows98 = ERRATIC
Date Fri, 20 Apr 2001 01:47:49 GMT

>Number:         7594
>Category:       os-windows
>Synopsis:       Apache + ActivePerl + Windows98 = ERRATIC
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    apache
>State:          open
>Class:          sw-bug
>Submitter-Id:   apache
>Arrival-Date:   Thu Apr 19 18:50:00 PDT 2001
>Originator:     andre.jesus@netc.pt
>Release:        1.3.19

I am trying to setup a development environment with Windows98. I don't know if the problems
I describe here also occur with WindowsNT or other windows versions.

After looking for answers in the newsgroups for this problem, I tried to isolate the situation
as best as I could. The answers in the newsgroups didn't work at all.

Briefly, I can't reliably execute CGIs. Sometimes they work, other times they don't (when
they don't they are served for download instead of executing).

This seems to me indicative of a bug in Apache and the way it handles the browser sessions.

Is this correct, or is there something you could advise?

Thank You
1. Have a functioning, default, ActivePerl installation.

2. Setup Apache with the original configurations (dont't change anything).

2a. Try the Apache configuration instructions for ActivePerl that come on their web site:
it doesn't work: scripts are treated as something for download.

3. Create purposefully a wrong shebang line in printenv.pl so that there is an Internal server
error: ex: #!/c:/perl/bin/perl.

4. After this, correct the shebang line, and next, in the same browser window where you got
the 500 error, refresh the page.

5. The script now works, and it works only in this browser session, not on other browser sessions,
and not other scripts either (ex: printenv2.pl, etc)!!!

6. Everything else, but I mean really everything else, including all that was written about
this subject in newsgroups, caused Apache to serve the script as something for download.
This seems to have something to do with the fundamental treatment of browser sessions that
handle scripts.
 [In order for any reply to be added to the PR database, you need]
 [to include <apbugs@Apache.Org> in the Cc line and make sure the]
 [subject line starts with the report component and number, with ]
 [or without any 'Re:' prefixes (such as "general/1098:" or      ]
 ["Re: general/1098:").  If the subject doesn't match this       ]
 [pattern, your message will be misfiled and ignored.  The       ]
 ["apbugs" address is not added to the Cc line of messages from  ]
 [the database 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!     ]

View raw message