Rails - Jan 2006 - HTML Fragment not Loading in Firefox; Fine Elsewhere

Ok, this has got me going a bit crazy. I have an HTML fragment being  
returned for the result to an AJAX query. It works fine in Safari or  
from curl (and even in IE/Mac), but utterly fails to load in Firefox,  
even if I point directly to the URL, skipping all that AJAX stuff in  
between. (The server logs show a 200 response, regardless of which  
browser is being used.) I''ve verified that there are no Javascript  
errors and have validated the HTML -- everything looks great.

I''ve opened up a port so that others can take a peek at it. Can  
anybody tell me why this URL won''t load in Firefox? Please? Pretty  
please?

http://seanmctex.homeip.net:3000/book/search?searchTerm=dragon

I''m utterly baffled by the strange behavior, and would love to get a  
handle on what''s going on here.

Thanks in advance for any help.

Sean
-----
Sean McMains
AIM: SeanMcTex
http://www.mcmains.net/ruminations


-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://wrath.rubyonrails.org/pipermail/rails/attachments/20060102/3ee610a1/attachment.html

Hi Sean,

I think it would be more helpful to paste in the parts of model, view,
controller that are causing the problem. Listmembers might then try to
reproduce your problem on windows or linux. Or maybe the ''second
pairs''
of eyes might even see the problem in the code...

apart from that

http://seanmctex.homeip.net:3000/book/search (without the parameter)

gets me the following error, so you rely on the searchTerm? What is
going on in book_query.rb and your book_controller.rb?:

 NoMethodError in Book#search

You have a nil object when you didn''t expect it!
The error occured while evaluating nil.gsub

RAILS_ROOT: public/../config/..

 Application
Trace | Framework
Trace | Full
Trace

/usr/local/lib/ruby/1.8/cgi.rb:342:in `escape''
#{RAILS_ROOT}/app/models/book_query.rb:13:in `search''
./public/../config/../app/controllers/book_controller.rb:13:in `search''

/usr/local/lib/ruby/1.8/cgi.rb:342:in `escape''
/usr/local/lib/ruby/gems/1.8/gems/actionpack-1.11.2/lib/action_controller/base.rb:853:in
`send''
/usr/local/lib/ruby/gems/1.8/gems/actionpack-1.11.2/lib/action_controller/base.rb:853:in
`perform_action_without_filters''
/usr/local/lib/ruby/gems/1.8/gems/actionpack-1.11.2/lib/action_controller/filters.rb:332:in
`perform_action_without_benchmark''
/usr/local/lib/ruby/gems/1.8/gems/actionpack-1.11.2/lib/action_controller/benchmarking.rb:69:in
`perform_action_without_rescue''
/usr/local/lib/ruby/gems/1.8/gems/actionpack-1.11.2/lib/action_controller/benchmarking.rb:69:in
`measure''
/usr/local/lib/ruby/gems/1.8/gems/actionpack-1.11.2/lib/action_controller/benchmarking.rb:69:in
`perform_action_without_rescue''
/usr/local/lib/ruby/gems/1.8/gems/actionpack-1.11.2/lib/action_controller/rescue.rb:82:in
`perform_action''
/usr/local/lib/ruby/gems/1.8/gems/actionpack-1.11.2/lib/action_controller/base.rb:369:in
`send''
/usr/local/lib/ruby/gems/1.8/gems/actionpack-1.11.2/lib/action_controller/base.rb:369:in
`process_without_session_management_support''
/usr/local/lib/ruby/gems/1.8/gems/actionpack-1.11.2/lib/action_controller/session_management.rb:116:in
`process''
/usr/local/lib/ruby/gems/1.8/gems/rails-1.0.0/lib/dispatcher.rb:38:in
`dispatch''
/usr/local/lib/ruby/gems/1.8/gems/rails-1.0.0/lib/fcgi_handler.rb:141:in
`process_request''
/usr/local/lib/ruby/gems/1.8/gems/rails-1.0.0/lib/fcgi_handler.rb:53:in
`process!''
/usr/local/lib/ruby/gems/1.8/gems/rails-1.0.0/lib/fcgi_handler.rb:52:in
`each_cgi''
/usr/local/lib/ruby/site_ruby/1.8/fcgi.rb:597:in `each''
/usr/local/lib/ruby/site_ruby/1.8/fcgi.rb:597:in `each_cgi''
/usr/local/lib/ruby/gems/1.8/gems/rails-1.0.0/lib/fcgi_handler.rb:52:in
`process!''
/usr/local/lib/ruby/gems/1.8/gems/rails-1.0.0/lib/fcgi_handler.rb:22:in
`process!''
public/dispatch.fcgi:24

/usr/local/lib/ruby/1.8/cgi.rb:342:in `escape''
#{RAILS_ROOT}/app/models/book_query.rb:13:in `search''
./public/../config/../app/controllers/book_controller.rb:13:in `search''
/usr/local/lib/ruby/gems/1.8/gems/actionpack-1.11.2/lib/action_controller/base.rb:853:in
`send''
/usr/local/lib/ruby/gems/1.8/gems/actionpack-1.11.2/lib/action_controller/base.rb:853:in
`perform_action_without_filters''
/usr/local/lib/ruby/gems/1.8/gems/actionpack-1.11.2/lib/action_controller/filters.rb:332:in
`perform_action_without_benchmark''
/usr/local/lib/ruby/gems/1.8/gems/actionpack-1.11.2/lib/action_controller/benchmarking.rb:69:in
`perform_action_without_rescue''
/usr/local/lib/ruby/gems/1.8/gems/actionpack-1.11.2/lib/action_controller/benchmarking.rb:69:in
`measure''
/usr/local/lib/ruby/gems/1.8/gems/actionpack-1.11.2/lib/action_controller/benchmarking.rb:69:in
`perform_action_without_rescue''
/usr/local/lib/ruby/gems/1.8/gems/actionpack-1.11.2/lib/action_controller/rescue.rb:82:in
`perform_action''
/usr/local/lib/ruby/gems/1.8/gems/actionpack-1.11.2/lib/action_controller/base.rb:369:in
`send''
/usr/local/lib/ruby/gems/1.8/gems/actionpack-1.11.2/lib/action_controller/base.rb:369:in
`process_without_session_management_support''
/usr/local/lib/ruby/gems/1.8/gems/actionpack-1.11.2/lib/action_controller/session_management.rb:116:in
`process''
/usr/local/lib/ruby/gems/1.8/gems/rails-1.0.0/lib/dispatcher.rb:38:in
`dispatch''
/usr/local/lib/ruby/gems/1.8/gems/rails-1.0.0/lib/fcgi_handler.rb:141:in
`process_request''
/usr/local/lib/ruby/gems/1.8/gems/rails-1.0.0/lib/fcgi_handler.rb:53:in
`process!''
/usr/local/lib/ruby/gems/1.8/gems/rails-1.0.0/lib/fcgi_handler.rb:52:in
`each_cgi''
/usr/local/lib/ruby/site_ruby/1.8/fcgi.rb:597:in `each''
/usr/local/lib/ruby/site_ruby/1.8/fcgi.rb:597:in `each_cgi''
/usr/local/lib/ruby/gems/1.8/gems/rails-1.0.0/lib/fcgi_handler.rb:52:in
`process!''
/usr/local/lib/ruby/gems/1.8/gems/rails-1.0.0/lib/fcgi_handler.rb:22:in
`process!''
public/dispatch.fcgi:24

Request

Parameters: None

Show
session dump

--- 
flash: !ruby/hash:ActionController::Flash::FlashHash {}

Response
Headers: {"cookie"=>[],
"Cache-Control"=>"no-cache"}

Regards

Jan

Sean McMains wrote:
Ok, this has got me going a bit crazy. I have an HTML
fragment being returned for the result to an AJAX query. It works fine
in Safari or from curl (and even in IE/Mac), but utterly fails to load
in Firefox, even if I point directly to the URL, skipping all that AJAX
stuff in between. (The server logs show a 200 response, regardless of
which browser is being used.) I''ve verified that there are no
Javascript errors and have validated the HTML -- everything looks great.

  I''ve opened up a port so that others can take a peek at it. Can
anybody tell me why this URL won''t load in Firefox? Please? Pretty
please?

  http://seanmctex.homeip.net:3000/book/search?searchTerm=dragon

  I''m utterly baffled by the strange behavior, and would love to
get a handle on what''s going on here.

  Thanks in advance for any help.

  Sean

-----

Sean McMains

AIM: SeanMcTex

http://www.mcmains.net/ruminations

_______________________________________________
Rails mailing list
Rails-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org
http://lists.rubyonrails.org/mailman/listinfo/rails


_______________________________________________
Rails mailing list
Rails-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org
http://lists.rubyonrails.org/mailman/listinfo/rails

Ok, I got this sorted out with the help of the very talented Seth
Dillingham. I had dropped in some puts commands, expecting that they''d
be logged somewhere. What I didn''t realize is that they were, instead,
being dumped to the http response. Firefox was seeing them at the top of
the headers and trying to interpret them as headers, which of course
drove it mad. I stripped those out so that all that was left was the
real headers, and everything''s working great now.

Sean

Sean McMains wrote:
> Ok, this has got me going a bit crazy. I have an HTML fragment being
> returned for the result to an AJAX query. It works fine in Safari or
> from curl (and even in IE/Mac), but utterly fails to load in Firefox,
> even if I point directly to the URL, skipping all that AJAX stuff in
> between. (The server logs show a 200 response, regardless of which
> browser is being used.) I''ve verified that there are no Javascript
> errors and have validated the HTML -- everything looks great.
-- 
Posted via http://www.ruby-forum.com/.