[Webkit-unassigned] [Bug 32829] New: The browser returns a blank page if the response code is HTTP 304.

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Mon Dec 21 11:13:26 PST 2009


https://bugs.webkit.org/show_bug.cgi?id=32829

           Summary: The browser returns a blank page if the response code
                    is HTTP 304.
           Product: WebKit
           Version: 528+ (Nightly build)
          Platform: Macintosh Intel
        OS/Version: Mac OS X 10.6
            Status: UNCONFIRMED
          Severity: Blocker
          Priority: P2
         Component: Page Loading
        AssignedTo: webkit-unassigned at lists.webkit.org
        ReportedBy: jnopporn at shiroyuki.com
                CC: jnopporn at shiroyuki.com


Defected versions
* Safari: 4.0.4
* Webkit: 532.7+
* Google: 4.0.249.43

When the web server with caching feature enabled returns HTTP 304, the browser
shows a blank page. When I use the web inspector, I found nothing in the
response body which is normal as any web server gives nothing back on HTTP 304.

Before reproducing:
To quickly reproduce the problem, you will need to know how to write Python
(http://python.org) and how to use Pylons web framework (http://pylonshq.com).
On Mac OS X, to install it, open Terminal (Terminal.app) and type "sudo
easy_install pylons".

How to reproduce:
0. Open the console or Terminal (or Terminal.app).
1. Create a Pylons application called "dummy_app" by running "paster create -t
pylons dummy_app" w/o quotes in your console.
2. Run "cd dummy_app && paster serve --reload development.ini" w/o quotes in
your console.
3. In your console, run "paster controller core" to create a controller called
"core" with only one method "index" where the method "index" returns "Hello,
World".
4. Then, open http://127.0.0.1:5000/core/index in both Firefox and Safari.
5. After successfully opening the page in both browsers, add
response.status=304 before the return statement in "def index" in
dummy_app/controllers/core.py to force the WSGI server to return HTTP 304.
6. Then, reload the page on both browsers.
X. Then, while I can see "Hello, World" displaying on Firefox, I see nothing on
Safari.

Expected result:
I should be able to see what I see on Firefox.

Notes and educational guesses:
1. I tried to compare on Firefox 3.5, Safari 4 (latest stable), nightly-build
Webkit and Google Chrome 4 beta for Mac. All Webkit-based browsers show me a
blank page.
2. My educational guess is that Webkit does not properly handle HTTP 304.
3. There are several bugs reported previously like Bug 25786
(https://bugs.webkit.org/show_bug.cgi?id=25786) and Bug 22084
(https://bugs.webkit.org/show_bug.cgi?id=22084). They might be related to the
problem. Or they might be caused by this problem.
4. The reproduction step is 100%. You will see the bug for sure.

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.



More information about the webkit-unassigned mailing list