This issue is definitely web-oriented. It's about the 'Content-Disposition' custom HTTP header which raised a big deal of concerns about security itself over time. As far as I currently understand it affects only web part(s) of Spring, more particularly spring-webmvc. It's not being used by Ignite. So I suppose it's safe to think that Ignite is not affected by that one.
-- Sent from: http://apache-ignite-users.70518.x6.nabble.com/
