|
Matt,
Did the HTTP error log give any details...I checked the "basic_error_logs" logs in the logs directory. If there
are other logs to check, please let me know where these are.
If not, start the server from the command like with the -vv...I did this and I found a spool file with what looks like trace data.
Before I had a chance to review this (and before I found where it was)
another programmer working on this problem made this discovery. In the
configuration file there is this line "ScriptAliasMatch
/ewalibcgitp/(.*).pgm /qsys.lib/ewalibcgit.lib/$1.pgm". Looking through
a trace log that the other programmer started he found a line that shows
"request filename = "/qsys.lib/ewalibcgit.lib/.pgm"". It looks like the
substitution variable $1 is being replaced with the program name. Which
now makes sense because we tweaked the configuration file yesterday and
now the 404 error says "The script request is not valid. The script is
not executable." This matches the "ScriptAliasMatch" line in the
configuration file and if the substitution is happening then the script
can't run.
Any thoughts on what would stop the substitution from happening?
Thanks,
Kent
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 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.