Anyone else experience problems with AJAX running in Firefox 3 (previously working scripts don't work in FF 3)? Anyone have a fix for it? So far all I've run accross is something to do with mod_security but I haven't checked it out yet.
Problems with AJAX with FireFox 3... Is there a fix?
Collapse
X
-
-
Haven't seen any issues with FF3, what's the url in question? might make it easier to debug what the issue is..Custom Software Development, email: woj#at#wojfun#.#com to discuss details or skype: wojl2000 or gchat: wojfun or telegram: wojl2000
Affiliate program tools: Hosted Galleries Manager Banner Manager Video Manager
Wordpress Affiliate Plugin Pic/Movie of the Day Fansign Generator Zip ManagerComment
-
Quite the opposite actually. Firefox actually aheres to standards much like Chrome, Opera, Safari and many other browsers. IE? Nope.
Anyway, many people have written AJAX modules but have failed to keep it updated with the changing times... try using Prototype if you can.
It continues to be updated and improved and works great with FF3.Comment
-
I did the google for: firefox mod_security
which returned some stuff with FF3 in the results, but I didn't go beyond that.
It might just be a server tweak. It's not uncommon that some browsers send different information when a request is made which could fuck stuff up. Example: accounting for IE turning image/jpeg into image/pjpeg. Fun times.Your post count means nothing.Comment
-
yeah.. can't find a "proper" fix but just disabled the content type check for my specific scripts and it's working... "apparently" it has something to do with FF adding a charset onto the end of the application/.... for POSTs and that gets filtered out by mod_security.. changing the regexp to take it into account would probably be the cleanest solution but I just want to get this damn thing working again for now.I did the google for: firefox mod_security
which returned some stuff with FF3 in the results, but I didn't go beyond that.
It might just be a server tweak. It's not uncommon that some browsers send different information when a request is made which could fuck stuff up. Example: accounting for IE turning image/jpeg into image/pjpeg. Fun times.Comment
-
I feel any and all pain you have but in regard to different "stuff".yeah.. can't find a "proper" fix but just disabled the content type check for my specific scripts and it's working... "apparently" it has something to do with FF adding a charset onto the end of the application/.... for POSTs and that gets filtered out by mod_security.. changing the regexp to take it into account would probably be the cleanest solution but I just want to get this damn thing working again for now.
I'll stop doing shit in quotes now.
Anyway ----
What javascript library do you use for Ajax?
Again, google searches seem to report issues you may be having: Content-Type / setting the encoding of the request / etc. There's got to be a decent solution, so here's a bump.Your post count means nothing.Comment

Comment