safari caching 303?

we are building an application, testing browser support. other browsers are fine, except for Safari on iOS 7 for form logins.

it seems Safari caches the 303 - SEE_OTHER response which the server sends for the first unauthenticated request. This leads to a redirect to login.html.

The HTTP standard says the following for 303 status codes:

10.3.4 303 See Other

The response to the request can be found under a different URI and SHOULD be retrieved using a GET method on that resource. This method exists primarily to allow the output of a POST-activated script to redirect the user agent to a selected resource. The new URI is not a substitute reference for the originally requested resource. The 303 response MUST NOT be cached, but the response to the second (redirected) request might be cacheable.

http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html

So the response must not be cached and here's the problem.

Could anyone from Apple confirms this?

regards,

-Derek