> > > Personally, I don't really think that a client side application running > havock on non-200 response is well behaving ... But given reality, we might > want to support such things.
fully agree. Vote for http://bugs.adobe.com/jira/browse/FP-251 ... > > In addition, we will only be able to support this to a certain point, in > particular we cannot prevent the servlet container from sending a non-200 > response. That's better than nothing. > So, what I can offer is the following: > > We support a special header asking for 200-only responses. The > SlingMaingServlet wraps the response such, that the setStatus code is > ignored. In this case, the response would also be set non-cacheable and a > log message (maybe even a request progress tracker entry) would be emitted > about this fact. > You mean, the setStatus is ignored for the HTTP status but it is put into the response body, right? Handling cache headers for the embedded Flash Player is also quite delicate: You must set it to e.g. "Cache-Control: no-store" and remove any Pragma headers. Many other configurations don't work (yes, it's <put in your favorite word for these kind of implementations>). Marc
