Hello Michael,
> I'm guessing that you have your xml declarations first. Its actually a generic format.xxx registration procedure so the framework can handle content-negotiation by default instead of the client having to describe it every time (I believe rails3 handle it with their responders from what Ive seen). But knowing that solves the problem... thanks... > I personally think this is a much better solution than what you're > describing here as you get proper content-negotiation rather than just > a fancy parser which somehow decides which of the equivalent entries > it should consider 'best'. Yes > I've seen IE saying it doesn't > support HTML or XML (new tab ie7) various plugins sending completely > malformed headers etc. The famous IE 'accept' problems... ie8 still has issues from what I have read. Thanks again, it solved the problem. Cheers guilherme -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en.
