That header has caused us nothing but trouble with new browsers. Any filenames with a space result in a double header being sent, which causes new browsers to not display the image.
Yep I mean file names for avatars. vBulletin keeps the original file name of the image, and if that name has commas (or sometimes spaces), it craps out on the new Chrome. Still testing with other browsers. Search Google for content disposition duplicate headers - it's definitely an issue vB needs to address if all browsers are headed in this direction, as we have no way of knowing what kind of file name a user might have for their uploaded photo (nor should it matter, in my opinion)
Yep I mean file names for avatars. vBulletin keeps the original file name of the image, and if that name has commas (or sometimes spaces), it craps out on the new Chrome. Still testing with other browsers. Search Google for content disposition duplicate headers - it's definitely an issue vB needs to address if all browsers are headed in this direction, as we have no way of knowing what kind of file name a user might have for their uploaded photo (nor should it matter, in my opinion)
Well that may be the case though I have not experienced it this is all of his avatars not showing up.
Well that may be the case though I have not experienced it this is all of his avatars not showing up.
What's weird is that even the image.php file (with no query strings) loads a broken image instead of vBulletin logo like anyone else. He could try replacing image.php with stock vB4 image.php & disable hooks. If the issue persists after both of those steps, I agree with all of you that this definitely seems like a server issue.
What's weird is that even the image.php file (with no query strings) loads a broken image instead of vBulletin logo like anyone else. He could try replacing image.php with stock vB4 image.php & disable hooks. If the issue persists after both of those steps, I agree with all of you that this definitely seems like a server issue.
I agree.
We do not have much background info either. was anything changed? Updated? Server updated? etc.. it is a guessing game right now but I would check server logs and ask your host what they updated recently.
We do not have much background info either. was anything changed? Updated? Server updated? etc.. it is a guessing game right now but I would check server logs and ask your host what they updated recently.
It would also help if we had a link to the site.
This is his site (recently posted on another thread) -
I have seen this issue before but I believe it was solved with a cache clearing and counter update. I am thinking it is not the server or other images would be effected.
I would move the images to the file system, update counters and clear caches and I bet that would fix it.
To troubleshoot I would also suggest trying a default theme and another sidebar block.
09-03-2014, 05:10 PM
Linear Mode
