With Apache 2 released and being the recommended version over the 1.3.x platform, I've recently been running some tests. The results were awesome, all my own scripts as well as a few commercial ones ran beautifully and everything was extremely smooth and fast. EXCEPT vBulletin that is
For some reason whenever ANY page produced by vBulletin is called I get a file download prompt - this happens regardless of whether it's a forum list, showing a thread, viewing a profile, etc. Looking at the file it downloads just produces garbage, no doubt the GZIPped data.
So, any thoughts on why vBulletin pages are causing a file download to occur instead of simply being interpretted by the browser? I realise PHP's support for Apache 2 is beta and perhaps (and hopefully) that might be the problem (and corrected with the final release), but with vBulletin being the only scripts having a problem and Apache 2 being the recommended version of Apache I'm keen to get this nipped
For some reason whenever ANY page produced by vBulletin is called I get a file download prompt - this happens regardless of whether it's a forum list, showing a thread, viewing a profile, etc. Looking at the file it downloads just produces garbage, no doubt the GZIPped data.
So, any thoughts on why vBulletin pages are causing a file download to occur instead of simply being interpretted by the browser? I realise PHP's support for Apache 2 is beta and perhaps (and hopefully) that might be the problem (and corrected with the final release), but with vBulletin being the only scripts having a problem and Apache 2 being the recommended version of Apache I'm keen to get this nipped
Comment