Issue 131691 in chromium: Some Chromeframe pages load from cache but should be showing fresh content

[chro...@googlecode.com]

Status: Untriaged
Owner: ----
Labels: Feature-ChromeFrame Type-Bug OS-Windows Pri-2

New issue 131691 by skunkopo...@gmail.com: Some Chromeframe pages load from
cache but should be showing fresh content
http://code.google.com/p/chromium/issues/detail?id=131691

ChromeFrame version:
19.0.1084.52 on MSIE 6 on WinXP
20.0.1132.27 on MSIE 7 on WinXP

Works as expected on:
MSIE 7 on WinXP
Chrome 19.0.1084.52 m on WinXP
Chrome 19.0.1084.54 on OSX Lion
Chrome 20 beta on Ubuntu 10.04


Related URL(s):
(secure app, requires login - IM for details if needed)
Chromeframe is enabled on pages through setting the X-UA-Compatible http
header


Steps to reproduce the issue:
1. user goes to a URL via button onclick action to submit form to action.
2. the destination URL can serve 2 versions of a page from the server,
based on the user's prefs (stored on the server)
3. navigate to URL - expect and receive version A
4. navigate away and change preference on server
5. navigate to URL (by clicking and submitting form again, not using
browser history)
6. look at page
7. right click in page and choose view-source


What do you expect to happen? What do you see instead?
at #6 I expect the see version B, but see version A, the cached version of
the page
at #7 I actually DO see version B of the page source - the view source and
visual rendering don't match


Additional Info
* there are no script errors - it's not like the page is loading but
breaking resulting in a different look, it's the old page showing
* clicking into the address bar and pressing [enter] to go to the page
again still shows the cached version
* pressing [F5] gets the new correct version B of the page
* MSIE cache is set to load new versions Automatically
* disabled all other dev related plugins with no difference (dynaTrace
AJAX, Fiddler, etc.)
* Chromeframe dev tools closes every page view even with the keep logger
open checkbox enabled, but Chrome standalone reports:
HTTP/1.1 200 OK
Server:
Cache-Control: no-cache, must-revalidate, max-age=0, no-store, private
P3P: CP="CUR OTR STA"
Pragma: no-cache
Expires: Thu, 07 Jun 2012 21:49:19 GMT
Content-Encoding: gzip
Content-Type: text/html; charset=UTF-8
Transfer-Encoding: chunked
Date: Thu, 07 Jun 2012 21:49:19 GMT

[chro...@googlecode.com]

Comment #1 on issue 131691 by skunkopo...@gmail.com: Some Chromeframe pages

load from cache but should be showing fresh content
http://code.google.com/p/chromium/issues/detail?id=131691

Here's a zip of the view-source results from 5 views of the same page.
1. from Chrome standalone looking at version A of the page
2. from Chrome standalone looking at version B of the page (adds a calendar
to the bottom)
3. from Chromeframe on IE7 looking at version A of the page (OK)
4. from Chromeframe on IE7 looking at version B of the page (source is OK,
but the rendered page still looks like version A, no calendar shown)
5. from Chromeframe on IE7 looking at version B of the page after pressing
F5 (source is unchanged except for a few dates and timing debug statement
values, but now the rendered page matches the source and the calendar is
drawn as expected)

Attachments:
view-source.zip 141 KB

[chro...@googlecode.com]

Updates:
Cc: robertsh...@chromium.org g...@chromium.org

Comment #2 on issue 131691 by dhar...@google.com: Some Chromeframe pages

load from cache but should be showing fresh content
http://code.google.com/p/chromium/issues/detail?id=131691

(No comment was entered for this change.)

[chro...@googlecode.com]

Comment #3 on issue 131691 by skunkopo...@gmail.com: Some Chromeframe pages

load from cache but should be showing fresh content
http://code.google.com/p/chromium/issues/detail?id=131691

Here's a File-SaveAs bundle for the app's page that submits the form to
load the page that is failing.

Unzip and open in Chromeframe and click the "Go" button next to "All
Accounts" to see the submit action.

It won't actually load since you aren't logged in, but just in case it
helps to see how we are attempting to call the resource that's getting
served from cache for this case.

Attachments:
launchpage.zip 319 KB

[chro...@googlecode.com]

Comment #4 on issue 131691 by jaytan...@skunkopotamus.com: Some Chromeframe

pages load from cache but should be showing fresh content
http://code.google.com/p/chromium/issues/detail?id=131691

Thought this might be a post/get cache confusion thing with GCF, but
happens in both cases, and I've verified the http headers are in the
message using GCF.

Confirmed that view-source doesn't match the visible page. It also doesn't
match inspect element from the right click context menu. Examined elements
show the cached page html in GCF, whereas in Chrome standalone the
view-source, visible page, and dev console all match.