Hi,
Marc Speck schrieb:
I've just read about SLING-613 and thought it's the right moment to raise
awareness about Flash/Flex limitations. Besides other limitations, Flash
cannot handle any HTTP status besides 200. A solution that has established
is to tunnel every response in status 200. For example, Alfresco Webscripts
handle this with a switch in the HTTP request header,
http://wiki.alfresco.com/wiki/Web_Scripts#Forcing_Success_Response_Status .
So it boils down to the question whether Flex/Flash support is an issue for
Sling?
I don't see a reason, why we should not support Flex/Flash.
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.
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.
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.
What do others think on this ?
Regards
Felix
Marc
