I'm trying to fix an issue where a user is unable to save changes in the backend as they are being kicked back to the admin login page even though they hasn't been logged in long enough for the session to have expired.
As they were trying to update a static block with an image via the WYSIWYG i looked there and was able to replicate the problem and found that a number of images aren't loading. looking in the Developer Tools for Chrome i see this
in the image above all those are meant to be images yet some have the type detected as text/html, the one i am hovering over clearly shows it's being loaded from the images directory and i can confirm it's a legit image (by locating the url in the DOM and getting the actual file that was supposed to load via the
<img>'s alt attribute).
this image was taken from Microsoft Edge's Developer Tools where i have a body tab when looking at a file in the network section, you can see a small bit of HTML which explains why the image is being detected as text/html, the HTML being what's generated when you're presented with the login page.
I believe the user being kicked back to the login page is related to these images not being loaded as images but as the admin login page as if i leave the page to another page (like manage customers) before the images start doing this i am not kicked back to the login page while if i wait i am.
My question is why are these images being loaded as the Admin Login page? and how can i fix this?
EDIT: we have a Dev Enviroment which uses the exact same code though database content is different as it has test data. there is a different with the Media Gallery but only by 8 images which combines is only ~0.4mb. the only difference between this dev and live enviroment is that Dev doesn't use membase and this Redis thing that's set up in the local.xml file in app/etc