Bug 31117 – Broken Keep-Alive Connection after getting 304-not-modified with content

• Status: RESOLVED
• Resolution: INVALID
• Component: Page Loading

Created attachment 42481 [details]
tar file containing html, php and png - needed to reproduce bug

If I request an Image which sends a 304 header and delivers a content (Bytes after the 0D 0A 0D 0A Sequence at the End of HTTP-Header), the Keep-Alive Connection is somehow broken, and the Browser is not able to send requests on this connection anymore.

i was able to reproduce the bug with the current stable Version of Safari on WinXP (531.9.1) and OS X 10.5 and on the current mobile-Safari on iPhone (User-Agent: "Mozilla/5.0 (iPhone; U; CPU iPhone OS 3_1_2 like Mac OS X; de-de) AppleWebKit/528.18 (KHTML, like Gecko) Version/4.0 Mobile/7D11 Safari/528.16")

How to reproduce:
- create a html-page, which references a php-generated image
- create a php-script, which outputs an image or sends a 304 if requested with if-modified-since-header. the script must send some bytes when responding the 304 - simply put some newlines after closing "?>" to archive this.

- request the html page 3 times (first time to get image into local cache, 2nd time to receive 304, 3rd time to see blank page)

Best Regards, Heiko

[Alexey Proskuryakov]

This is a great bug report!

HTTP connections are not managed by WebKit, networking libraries below it implement it. In case of Safari, the libraries are closed source, and reports about those should be directed to <http://bugreport.apple.com> (free registration is required).

Would you be willing to report this bug to Apple? I think that there were related issues reported before, but the simple test case here is of exceptional value.

Thanks for Your quick reply! I reported the bug to Apple.

[Alexey Proskuryakov]

That's <rdar://problem/7367343>, for any Apple person who wants to check it out.