Hide Forgot
(only unreleased develop) Steps to reproduce: 1. Open the recipe page for a recipe which is running or queued 2. Wait > 30 seconds (this is the polling interval at which the page automatically re-fetches its JSON model) 3. Close the tab 4. Press Ctrl-Shift-T to reopen the closed tab Expected results: should see the page Actual results: shows a pile of JSON
One thought I had was that we should be setting Vary: Accept since we are doing content negotation for /recipes/123. We should probably just set it globally on all responses (apart from static files anyway) since we expect to do content negotiation in most or all of our new endpoints. Not sure if that will fix this problem though.
(In reply to Dan Callaghan from comment #1) > One thought I had was that we should be setting Vary: Accept since we are > doing content negotation for /recipes/123. We should probably just set it > globally on all responses (apart from static files anyway) since we expect > to do content negotiation in most or all of our new endpoints. > > Not sure if that will fix this problem though. Setting Vary:Accept fixes the problem. I have verified it on both Firefox and Google Chrome. http://gerrit.beaker-project.org/#/c/4784/
(In reply to matt jia from comment #2) > (In reply to Dan Callaghan from comment #1) > > One thought I had was that we should be setting Vary: Accept since we are > > doing content negotation for /recipes/123. We should probably just set it > > globally on all responses (apart from static files anyway) since we expect > > to do content negotiation in most or all of our new endpoints. > > > > Not sure if that will fix this problem though. > > Setting Vary:Accept fixes the problem. I have verified it on both Firefox > and Google Chrome. > > http://gerrit.beaker-project.org/#/c/4784/ Repost with correct branch http://gerrit.beaker-project.org/#/c/4789/
Beaker 23.0 has been released.