Re: Problem with CGI from Browser (Resolved)

After additional testing with this customer, we were able to confirm that this was, in fact, a security problem.  The joblog was throwing an MCH1001 on access to the application library specified as the CGI library.  The solution was to grant access to QTMHHTP1 at the library level, but this raises a question.  The library is secured with an authorization list and the QTMHHTP1 user profile (along with QTMHHTTP) is granted *ALL access in that authorization list.  Why was that not sufficient?

Rich Loeber - @richloeber
Kisco Information Systems
http://www.kisco.com

------------------------------------------------------------------------



On 5/27/2020 3:16 PM, Brad Stone wrote:

Do think maybe it got corrupted?

Are you using CGIDEV2? If so, the error log it puts out is usually pretty
useful.



On Wed, May 27, 2020 at 1:21 PM Rich Loeber <rich@xxxxxxxxx> wrote:

That is what I do too. The first output to the new page is ALWAYS the
http header. Twenty three bytes that looks like this: 'Content-type:
text/html' with two crlf's following it.

Rich Loeber - @richloeber
Kisco Information Systems
http://www.kisco.com

------------------------------------------------------------------------



On 5/27/2020 1:58 PM, Brad Stone wrote:

How do you handle the headers? That's what it seems to be
complaining about.