×

Good News Everybody!

The new search engine is LIVE!

Please report any problems to david (at) midrange.com.




As I have said in an earlier post, I have been running a persistent CGI
application on a V5R1 system for ten or more years using the IBM original
HTTP server. I have now transferred it to a V5R3 system and must run it
under Apache. My static pages work correctly but I am having problems with
my dynamic persistent CGI pages. The first screen is displayed correctly
with data retrieved from the database, so I assume that there are no
security problems, yet, when I click on Enter to access the second screen,
I get an error, the actual error depending on which particular version of
my config file I use.

I imagine that the problem is of my making, but, having reacted to various
kind suggestions, as yet I have achieved nothing, and I have to admit that
I really don't know what I am doing. Yet, having searched for many hours
for adequate documentation of the syntax of Apache directives, I cannot
find anything that answers my questions.

For instance, what is the effect of putting *^* at the beginning of a
ScriptAlias or ScriptAliasMatch line? What is the difference between a
ScriptAliasMatch statement that ends with $1 and another that ends $1.pgm?

https://www.easy400.net/cgidev2o/persista.htm states -

“The *ScriptAliasMatch *directive for executing persistent CGI programs
MUST HAVE the following format
ScriptAliasMatch /cgidev2p/(.*) /qsys.lib/cgidev2.lib/$1
The following format WOULD NOT WORK:
ScriptAliasMatch /cgidev2p/(.*).pgm /qsys.lib/cgidev2.lib/$1.pgm”

but neither work for me.

Can anyone please point me at documentation of the Apache syntax that
explains all this?

Many thanks,

Rob

This thread ...

Follow-Ups:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2026 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.