[WEB400] persistent CGIDEV2 problem - ERROR code 500 -- MIDRANGE-L

Good News Everybody!

The new search engine is LIVE!

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

Subject: [WEB400] persistent CGIDEV2 problem - ERROR code 500
From: Rob Dixon <robertsdixon@xxxxxxxxx>
Date: Wed, 30 Oct 2013 14:50:35 +0000
List-archive: <http://archive.midrange.com/midrange-l>
List-help: <mailto:midrange-l-request@midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.midrange.com>
List-post: <mailto:midrange-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=unsubscribe>

I have been using persistent CGIDEV2 for several years, using OS/400 V5R1
and the original HTTP server, without any real problems and it works very
well, with excellent performance. However, if a user uses his browser back
button and then operates on the previous window, I get ERROR code 500. It
seems that when this happens the system starts a new DEFAULT job under
QHTTPSVR. This does not have the correct library list etc. so would be
bound to crash. I want the new request to return to my existing job as
would normally be the case. I am sure that other users of persistent
CGIDEV2 must have had this problem and presumably have solved it.

Any suggestions please?

Rob Dixon

www.erros.co.uk
www.boarstall.com

Follow-Ups:

Re: [WEB400] persistent CGIDEV2 problem - ERROR code 500 , Paul Raulerson
Re: [WEB400] persistent CGIDEV2 problem - ERROR code 500 , Rob Dixon

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.