Debugging exhibits is painful because of caching

The actual exhibits list at:

https://software-center.ubuntu.com/api/2.0/exhibits/en/

is cached, but I'd be surprised if we were caching the banner urls included there. I think we'll need to investigate a bit more to find out why USC doesn't see the images.

One thought is that when the image is uploaded and made available on ServerA (and uploaded to the ftp server using the ftp storage), it is *not* available on ServerB until there is a request from the application itself for the image url - but it needs investigation that I can't do now :P

Meh, LP ate my comment. So again:
I reassigned this for now to the server, we can add code to the client to call webkit_web_view_reload_bypass_cache()
when a debug env is set, but I am not sure if the reverse proxy setup we have will honor this or not. This sounds like
a server side issue to me, but I'm happy to fix in the above way if that is honored by the caches.

I don't know what I had understood initially (comment 1), but afaics, the issue is simply that the exhibits URL requested by the client :

https://software-center.ubuntu.com/api/2.0/exhibits/en/

is cached for 5 minutes, which is painful for testing new exhibits? At least, that matches the solution mpt has proposed in the description, which would work too? ie.:

{{{
$ REQUEST_FRESH_EXHIBITS=true software-center
}}}

would, when requesting exhibits, use a URL like:

https://software-center.ubuntu.com/api/2.0/exhibits/en/?nocache=abcd-some-random-sha1

Let me know if there's something the server could do otherwise which would help?

Mpt I have assigned this to you for now. If you figure out an answer noodles then we can clear this off or set a level. Please assign it to me once you are done. Many thanks.

Sorry, I don't understand why this is assigned to me.