Caching policy prevents JavaScript changes for clients

[patritzenfeld]

There seems to be a problem after #73. No matter what is submitted, the image will not be displayed. Instead a generic message, "Sorry! Your program couldn't be run right now.", is shown:

[patritzenfeld]

Don't know if that is relevant, but the url contains this after codeworld/haskell:
#:%20[1%20of%201]%20Compiling%20Main%20%20%20%20%20%20%20%20%20%20%20%20%20(%20program.hs,%20program.js_o%20):%20Linking%20program.jsexe%20(Main)

When the run button is activated.

[nimec01]

This seems to be a caching problem. Take a look at the codeworld.js script in Dev Tools (Sources tab). You will probably still see the old version. Clearing site data or refreshing the page with cache disabled will then fix the problem.

But I should still investigate where this caching policy is being set.

[jvoigtlaender]

And maybe some action should be taken to invalidate all previous caches on clients?

Otherwise, it's bound to happen (unless there is some automatic time-limiting of caches in browsers) that some students will experience CodeWorld not working for them (because they have something in their browsers' caches that surfaces this problem).

[patritzenfeld]

I can confirm everything works as expected after clearing the cache.

[patritzenfeld]

It seems #77 did not correctly apply to the scripts. When I inspect them, only the HTML page has no-cache set, but the resources don't:

Page

JS

I had to clear cache again to see the changes from #76

[nimec01]

It works for me.

Also works in curl.

[nimec01]

(Well I have Disable cache enabled in Dev Tools so that will explain why it did work for me directly)

I guess that client did not request the resource again since it is cached? So we would need to enforce a refresh somehow.

[patritzenfeld]

Seems like it. I can only see no-cache on the files when disabling the cache on reload via CTRL + F5.