|
X'15' is the wrong code. Although the Web server still converts it to the right PC CCSID character it is doing so "manually". You should always use X'25' for you linefeeds, and X'2525' for two line feeds. When you send multiple HTTP headers, you end each one with a single X'25' and the last one with two, X'2525'. Normally HTML/CGI examples use the \n symbol to represent where the X'25' goes. I sent this example earlier today, just replace the \n with X'25' in your RPG IV code. Content-type: text/html\n Cache-Control: no-cache\n Pragma: no-cache\n Expires: 0\n\n -Bob Cozzi www.RPGxTools.com RPG xTools - Enjoy programming again. -----Original Message----- From: web400-bounces@xxxxxxxxxxxx [mailto:web400-bounces@xxxxxxxxxxxx] On Behalf Of Joe Giusto II Sent: Thursday, January 26, 2006 6:23 PM To: Web Enabling the AS400 / iSeries Subject: Re: [WEB400] Prevent Browser From Going Back To Credit Card Page thank you. I will try again. the first time I tried it before any HTML, I got an error about not being able to display the page. I must have had something else wrong. do I still need the 2 newline entries after CONTENT-TYPE: TEXT/HTML or do I put these statements directly after and then do the 2 newline (x'15') characters? ----- Original Message ----- From: <Matt.Haas@xxxxxxxxxxx> To: <web400@xxxxxxxxxxxx> Sent: Thursday, January 26, 2006 8:52 AM Subject: Re: [WEB400] Prevent Brower From Going Back To Credit Card Page They are *NOT* HTML headers, they are HTTP headers. You need to send them before you write any HTML out. Matt -----Original Message----- From: web400-bounces@xxxxxxxxxxxx [mailto:web400-bounces@xxxxxxxxxxxx] On Behalf Of Joe Giusto II Sent: Wednesday, January 25, 2006 5:45 PM To: Web Enabling the AS400 / iSeries Subject: Re: [WEB400] Prevent Brower From Going Back To Credit Card Page Do these go before the <HEAD> tag? ----- Original Message ----- From: <Matt.Haas@xxxxxxxxxxx> To: <web400@xxxxxxxxxxxx> Sent: Wednesday, January 25, 2006 4:49 PM Subject: Re: [WEB400] Prevent Brower From Going Back To Credit Card Page <SNIP> Another thing you can do (you should actually do this anyway since you don't want transactional data cached) is make sure that you're doing a POST and write out the expire HTTP headers (these go after the Content-Type header): Cache-Control: no-cache Pragma: no-cache Expires: 0 When a person hits the back button, they'll get an error about expired data.
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.