Try with another browser. Maybe Mozilla doesn't take into account the HTTP headers as it should, and it puts the pages on cache. If it does this because of a bug or because it is a very bad browser, you cannot stop it.
Teddy, Teddy's Center: http://teddy.fcc.ro/ Email: [EMAIL PROTECTED] ----- Original Message ----- From: "Alexander Blüm" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Sunday, July 06, 2003 3:11 PM Subject: Re: Re: disabling the use of browser history Octavian Rasnita wrote: > This doesn't work right every time. > A better idea is to put the HTTP headers in the real HTTP header like: > > print <<"EOF"; > Content-type: text/html > Pragma: no-cache > Cache-control: no-cache > Expires: Thu, 01 Jan, 3200 10:10:10 GMT > > EOF true, now I used $r->no_cache(1); $r->send_http_header('text/html'); since I'm using mod_perl, and it does send the wanted headers: Connecting to 192.168.0.11:80... connected. HTTP request sent, awaiting response... 1 HTTP/1.1 200 OK 2 Date: Sun, 06 Jul 2003 11:40:21 GMT 3 Server: Apache/1.3.27 (Unix) mod_perl/1.27 4 Pragma: no-cache 5 Cache-control: no-cache 6 Keep-Alive: timeout=15, max=100 7 Connection: Keep-Alive 8 Content-Type: text/html 9 Expires: Sun, 06 Jul 2003 11:40:21 GMT 200 OK BUT: I can still go back and forth... The browser I use is Mozilla, maybe that's a different story... well, I followed the access log, and when I do go back and forth, there are really no "GET"'s nor "POST"'s - the browser still chaches the data... are there other ways? > > ----- Original Message ----- > From: "Greenhalgh David" <[EMAIL PROTECTED]> > To: "Alexander Blüm" <[EMAIL PROTECTED]> > Cc: <[EMAIL PROTECTED]> > Sent: Sunday, July 06, 2003 9:17 AM > Subject: Re: disabling the use of browser history > > > <head> > .... > <META http-equiv="Pragma" content="no-cache"> > .... > </head> > > HTH > > Dave > > > On Saturday, July 5, 2003, at 10:12 pm, Alexander Blüm wrote: > > >>hello!!! >> >>I'm writing a database frontend based on perl-CGI. >> >>Each query is being cached in a file with the current session-ID. The >>reason for this doing is that some queries do take a very long time to >>process and have a large output. If I want to see the next 50 results >>using the SQL 'LIMIT' and 'OFFSET' option this would require to rerun >>the query, which is unnecessary, since the database is used rarely. >> >>Either way, I need to disable the use of the browsers function to "go >>back" or "forward" - it may result in unexpected or wrong outputs. >> >>wasn't this done somehow with the HTML headers or javascript? >> >>I remember something with the word "expire"... >> >>Any help would be greatly appreciated. >>TIA >> >> >>cheers, >>Alex >> >> >>-- >>To unsubscribe, e-mail: [EMAIL PROTECTED] >>For additional commands, e-mail: [EMAIL PROTECTED] >> > > > > -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
