ispyppc

Ok, so I have seen TONS of these errors all over Google, but not one single person ever really explained what the REAL PROBLEM was. Some of the previous solutions work if you’re using .htaccess to password protect the directory — but many are not protecting their directories. Some of the previous solutions will work if you’re on Godaddy Hosting — but many are not on godaddy hosting, so fastcgi isn’t the problem. So what could be the main problem?

FOR ME, THIS WAS THE MAIN PROBLEM: mod_security

On Apache, mod_security BLACKLISTS ^Shockwave Flash at REQUEST_HEADERS:User-Agent. Nearly 99.9% of apache servers have this setup as default. This is what the flash uploader from wordpress uses as the user-agent when it’s being used.

This is a simple fix — just have your hosting company WHITELIST ^Shockwave Flash in mod_security. It’s blacklisted as a spambot by default — so if you change it (or your host does), you will no longer have this problem.

This is NOT a browser issue, not an OS issue, etc. It’s just being blacklisted, that’s all. Take note, servers upgrade their apache software (including mod_security) all the time — and the newer versions might overwrite your current rules. So if this happens again later on down the road, then you know you need to whitelist ^Shockwave Flash again (if and when you get that silly http error ever again.)

FYI: I discovered this because the http error is a 406 error, which is what made me look at the log files of mod_security. 406 errors should never really occur unless something is blacklisted.

Call your host or do it yourself if you have a dedicated server. Trust me, this should fix the problem if you’ve tried everything else and none of it worked. ??

Ok, so I have seen TONS of these errors all over Google, but not one single person ever really explained what the REAL PROBLEM was. Some of the previous solutions work if you’re using .htaccess to password protect the directory — but many are not protecting their directories. Some of the previous solutions will work if you’re on Godaddy Hosting — but many are not on godaddy hosting, so fastcgi isn’t the problem. So what could be the main problem?

FOR ME, THIS WAS THE MAIN PROBLEM: mod_security

On Apache, mod_security BLACKLISTS ^Shockwave Flash at REQUEST_HEADERS:User-Agent. Nearly 99.9% of apache servers have this setup as default. This is what the flash uploader from wordpress uses as the user-agent when it’s being used.

This is a simple fix — just have your hosting company WHITELIST ^Shockwave Flash in mod_security. It’s blacklisted as a spambot by default — so if you change it (or your host does), you will no longer have this problem.

This is NOT a browser issue, not an OS issue, etc. It’s just being blacklisted, that’s all. Take note, servers upgrade their apache software (including mod_security) all the time — and the newer versions might overwrite your current rules. So if this happens again later on down the road, then you know you need to whitelist ^Shockwave Flash again (if and when you get that silly http error ever again.)

FYI: I discovered this because the http error is a 406 error, which is what made me look at the log files of mod_security. 406 errors should never really occur unless something is blacklisted.

Call your host or do it yourself if you have a dedicated server. Trust me, this should fix the problem if you’ve tried everything else and none of it worked. ??