Hi Marc,
Marc Speck schrieb:
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 ...
ok
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>).
Hmm, we can of course inspect the HTTP version of the request and not
send the Pragma header. Regarding the Cache-Control: I would think, we
would just set about any no-* flag on that header. This should not bomb ...
If requirements get too specific, I would suggest to introduce a request
level filter, which implements this kind of functionality, it would be
easier and better to handle anyway I think ...
Regards
Felix
