> a standard HTTP request is a GET request. I guess I'm just missing some basic definition of terminology. Been writing desktop systems for too long, 'spose.
> using firefox and one of a number of extensions (firebug springs to mind) > you can actually view the request headers that are sent. Firebug shows headers for the c3.php page are: Response Headers: Date Sun, 16 Dec 2007 20:48:43 GMT Server Apache/2.2.6 (Fedora) X-Powered-By PHP/5.1.6 Expires Thu, 19 Nov 1981 08:52:00 GMT Cache-Control no-store, no-cache, must-revalidate, post-check=0, pre-check=0 Pragma no-cache Content-Length 51 Connection close Content-Type text/html; charset=UTF-8 Request Headers: Host localhost User-Agent Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1.6) Gecko/20070812 Remi/2.0.0.6-1.fc6.remi Firefox/2.0.0.6 Accept text/xml,application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5 Accept-Language en-us,en;q=0.5 Accept-Encoding gzip,deflate Accept-Charset ISO-8859-1,utf-8;q=0.7,*;q=0.7 Keep-Alive 300 Connection keep-alive Referer http://localhost/hf/c1.php Cookie PHPSESSID=spave8i7jc7m0cmmvcdaj3msh7 > > > > (P.S. I'll get to the issue of rearchitecting this via require instead > > of using header() redirects,cough, cough, Richard Lynch, cough, cough > > :) in a future message. One step at a time...) > > yes - abusing redirects as described is wasteful. and certainly it's the > first time I've ever heard the statement 'Never show pages in response to > POST' > sounds like hubris too me. I've seen the statement in a number of messages in the archives here and in google searches. Probably a case of Read Once, Repeat Often. I took it with a grain of salt. They are java guys over there, after all. :) OK, now onto ridding the world of these redirects().... -- RE, Chicago -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
