Apple has the power to change the web on a whim. If this isn't fixed it could cause almost every web-service to actually send a `Cache-Control: no-cache` header on it's POST responses. A long shot, but maybe they are doing this deliberately (like they did with <video> vs flash) for some reason?
Pretty unlikely, especially undocumented anywhere. I'd ascribe that to stupidity rather than malice and would guess they tried to change something in the caching subsystem (e.g. cache POST with an explicit cache-control spec — makes sense for a mobile phone) and they broke the default case.
This would be supported by max-age: 0 failing to make resources "uncacheable".
