Hi everyone,
This little patch will fix Chrome behavior, which I discovered recently. When you navigate to API page, you will get XML version of API.
This is because Chrome sending 'application/xml' mime type before 'text/html' (which is weird but standard correct). Unfortunately, we are lacking 'q' parameter handling in 'respond_to' plugin to handle this correctly...