Thanks for the ideas to use middleware to compress the response and to pre-parse the URL, but i think i would like that it be possible for the application to parse URLs with multiple extensions as well.
If multiple extensions are not considered a 'bad practice' and if they can be used to indicate 'composite formats', for the use by middleware for example, why not to allow rails to take multiple extensions into account as well? Also, the views are generated by the application, so the application has to know anyway at which url and with which Accept header to access zipped CSV or PDF, to be able to generate a correct link or button element. So compression cannot be viewed as just an optional middleware configuration independent of the applicaiton. If multiple extensions are discouraged and i need to use Accept header, then a. how to set it from an html <a> element? (I've seen that in HTML5 there is the "type" attribute, but i've read "it is purely advisory", does it work?) b. URL does not anymore determine the response completely, which i do not like. c. requesting /users.csv with Accept header application/zip looks to me either strange or no better than requesting /users.csv.zip directly. -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To view this discussion on the web visit https://groups.google.com/d/msg/rubyonrails-core/-/3_SmtqcKsVcJ. 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.
