I was having ajax problems with a certain combination of Firefox 3.5.x
and Firebug. Can't remember which versions exactly, but I do recall
that unchecking the "Show XMLHttpRequests" option in the Console tab
made the problem go away.
--Karl
On Sep 8, 2009, at 2:41 PM, Mike McNally wrote:
For what it's worth, I have a whole application that works just fine
with AJAX form posts from FF3, and I didn't have to do anything at all
to make it work. It'd be interesting to learn what back-end software
is involved (Java/Stripes in my case).
On Tue, Sep 8, 2009 at 12:03 PM, RPrager<ryan.pra...@gmail.com> wrote:
Mine won't even work in FF3 if I use the GET method. I'm currently
working with the developer to get to the bottom of this. I will post
if I find a solution. In the meantime, keep the suggestions coming if
you have them. Thanks!
On Sep 8, 5:19 am, Karl Hungus <coldnebraskab...@googlemail.com>
wrote:
Yes - me. Exactly the same problem as you. FF3.x not liking an Ajax
form post.
It works if I change the POST to a GET, but that is a bit pants to
be
honest. I suspect its a FF3 issue, but don't know what.
Did you get to the bottom of it ?
Rgds,
KH.
On 4 Sep, 17:20, RPrager <ryan.pra...@gmail.com> wrote:
I'll see if I can take a look at server log files. Has anybody else
experienced problems using ajax with FF3? Any other ideas are
appreciated. Thanks
On Sep 4, 10:10 am, Mike McNally <emmecin...@gmail.com> wrote:
Well frankly that's not looking like a jQuery problem to me. Your
*server* is returning different results. I have no idea why,
but I
don't see what jQuery (or anything else at the client) is
supposed to
do about that. Do you have debug logging or other debug
facilities at
the server to see what's going on?
On Fri, Sep 4, 2009 at 10:04 AM, RPrager<ryan.pra...@gmail.com>
wrote:
Here is the only difference I found in the Request Headers:
FF2: Content-Type application/x-www-form-urlencoded
FF3: Content-Type application/x-www-form-urlencoded;
charset=UTF-8
Any ideas?
On Sep 4, 9:47 am, RPrager <ryan.pra...@gmail.com> wrote:
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.
--
Turtle, turtle, on the ground,
Pink and shiny, turn around.
--
Turtle, turtle, on the ground,
Pink and shiny, turn around.
