Forum: Ruby on Rails HTML Fragment not Loading in Firefox; Fine Elsewhere

Announcement (2017-05-07): www.ruby-forum.com is now read-only since I unfortunately do not have the time to support and maintain the forum any more. Please see rubyonrails.org/community and ruby-lang.org/en/community for other Rails- und Ruby-related community platforms.
Sean McMains (Guest)
on 2006-01-02 08:14
(Received via mailing list)
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?searc...

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 (Guest)
on 2006-01-02 18:51
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.
This topic is locked and can not be replied to.