Firefox 3 response:
<HTML><BODY><HR>
<H1 ALIGN=CENTER>Not available at present</H1>
<P>Status code = NL
<!-- NL --><HR></BODY></HTML>
According to our back end developer, the NL = 'Null execution'.
Meaning that the page (newcoleng) was launched without any input at
all.
I.e., neither a <FORM> nor any positional parameters. The page is at a
loss as to how to serve my needs.
Firefox 2 response (this is not the exact full response because it
would be rather large):
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 1.0 Transitional//EN" "http://
www.w3.org/TR/xhtmll/xhtmll-loose.dtd">
<html><head><title>Page Title</title></head><body>This page was a
success</body></html>
I just realized that the Firefox 2 response included the DOCTYPE while
Firefox 3 did not.
Thanks for the help.
On Sep 3, 9:59 pm, "emmecin...@gmail.com" <emmecin...@gmail.com>
wrote:
> Well what exactly is the error? What is different about the server
> response from FF2 vs. FF3?
>
> On Sep 3, 9:04 pm, RPrager <ryan.pra...@gmail.com> wrote:
>
> > I've been using Firebug. The data that my browser is sending looks as
> > expected.
>
> > Here is the information from firebug:
>
> > Response Headers
> > Date: Fri, 04 Sep 2009 01:54:24 GMT
> > Server: Apache/2.2.6 (Fedora)
> > Content-Length: 179
> > Connection: close
> > Content-Type: text/html
>
> > Request Headers
> > User-Agent Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:
> > 1.9.0.13) Gecko/2009073022 Firefox/3.0.13
> > Accept */*
> > 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
> > Content-Type application/x-www-form-urlencoded; charset=UTF-8
> > X-Requested-With XMLHttpRequest
> > Content-Length 24
> > Pragma no-cache
> > Cache-Control no-cache
>
> > Post
> > F10 Yes
> > F11 No
>
> > Any ideas why Firefox 3 would be having issues with my ajax request?
>
> > On Sep 3, 3:34 pm, "emmecin...@gmail.com" <emmecin...@gmail.com>
> > wrote:
>
> > > You **must** install and use something like Firebug or TamperData to
> > > see what your browser is sending to the server, and what your server
> > > is sending back. Just because the HTML response content looks like an
> > > error does not necessarily mean that the HTTP response contained an
> > > error code (for example).
>
> > > On Sep 3, 1:29 pm, RPrager <ryan.pra...@gmail.com> wrote:
>
> > > > I just tested this code using FF2 and it works just fine. This appears
> > > > to be a FF3 problem only. I'm currently using Firefox version 3.5.2.
> > > > Any ideas?
>
> > > > On Sep 3, 10:31 am, RPrager <ryan.pra...@gmail.com> wrote:
>
> > > > > Thanks for the idea but adding (dataType: 'text') did not produce a
> > > > > different result.
>
> > > > > On Sep 3, 9:32 am, 月讀 <keyoft...@gmail.com> wrote:
>
> > > > > > My english is not well.
>
> > > > > > $.ajax({
> > > > > > type: "POST",
> > > > > > url: "newcoleng",
> > > > > > data: "F10=Yes&F11=No",
> > > > > > dataType: 'text',
> > > > > > success: function(data){
> > > > > > alert( "Data Saved: " + data );
> > > > > > }
>
> > > > > > });
>
> > > > > > Try it.
