How to find out what type of caché the server is using

Or is it a new web browser trend?

[explorador]

Hi, I'm not sure where to put this but I'm having some problems with the server regarding cache.

The problem:I'm modifying some stuff on the html and css of a website but there is some kind of cache driving me nuts. The html takes 5 minutes aprox to go away and let me see the real page and CSS, so the CSS mods are not appearing on the site. Even the images appear as the old ones when I update them. Even worse: if I delete any JPG it will still show on the browser despite not existing on the server. I have to add something like widget.jpg?123random to make the new image appear.

I'm not using cache, the htaccess is clean. The problem appeared like 3 weeks ago on my server A, I noticed due to some modifications I had to do there. NOW I'm seeing the same problem on server (diff company) who knows since when but I'm getting it from last week. I know it could be a cache thing both companies implemented, or by the date (coincidence?) it could be a new cache trend. I'm using Firefox 25 and Opera 12.6.

Is there a way to find out what kind of dark magic is in between?

Thanks in advance.

[aakk9999]

It could also be some kind of intermediate proxy caching.

Have you tried to see what happens with a page or an image if you return Cache-Control: no cache, no store ?

[phranque]

the first thing i would try is to install the HTTP Live Headers add-on for firefox and examine all the HTTP Request and Response headers.

then try accessing your content through a different ISP if possible to rule out proxy caching.
you might try mobile access.

[explorador]

Thanks aakk9999 and phranque, I'm using Live Headers now. The modifications I made to the htaccess yesterday were not working at all, but today they do. I guess the htaccess got cached too in some way because the cache mods in it were not recognized despite clearing the cache, history, etc.

I've seen at times that some mods cause errors and even removing the mods still brings the same error, the same thing as mentioned before: as if the old htaccess remains active on the browser.

It is now working. Thank you.