2009/9/9 RPrager <ryan.pra...@gmail.com>: > FF3 output: > > <HTML><BODY><H1>logcgis</H1>Can not access CGI data: Script can only > be used to decode form results > <BR>There are 0 positional parameters and 0 CGI fields > </BODY></HTML> > > FF2/IE output: > > <HTML><BODY><H1>logcgis</H1> > <BR>There are 0 positional parameters and 2 CGI fields > <BR>CGI 'F10' equals 'Yes' > <BR>CGI 'F11' equals 'No' > </BODY></HTML> >
At this stage I would suggest digging into the actual HTTP traffic, not with Firebug (which, being inside the browser, doesn't necessarily give an accurate view of things) but with an HTTP debugging proxy. If you're on Windows you can use Fiddler <http://www.fiddler2.com/fiddler2/>; on other platforms (as well as Windows) the trial version of Charles <http://www.charlesproxy.com/> is worth a look. Enable one of these tools (you have to install a Firefox extension for each of them to autoconfigure - both their sites make this stuff easy to find) and you'll be able to see the actual content of your request. If the body of the request contains the form data then the problem is on the server; if not, then the problem is on the browser. If the problem is on the browser then more digging will be required, but if it's on the server then the information about the whole request (headers and body) will help the server-side developer work out what's going on. Regards, Nick. -- Nick Fitzsimons http://www.nickfitz.co.uk/
