As of late a few of our clients moved their sites to a VPS (Virtual Private Server) running 64-Bit CentOS, WHM, cPanel, Apache 2.2, PHP 5.3, and My SQL 5.x, This move was activated by their craving to show signs of improvement execution and more prominent control out of running their own facilitated web condition and the VPS appeared the best fit at that point. By and large their move went superior to expected with no serious issues. In any case, one blunder that they saw that happened over and over when they attempted to utilize the Flash Uploader in WordPress, was the feared HTTP Error.
Streak Uploader in WordPress HTTP Error:
I’ll consider this HTTP Error the feared mistake, on the grounds that in the wake of examining for a considerable length of time, attempting all the different proposed fixes, and having nothing work reliably our clients approached us for some assistance with the blunder we did some exploration for them lastly unearthed a site that gave us enough data to address the issue.
As a matter of first importance:
Let me bring up that this mistake IS RELATED to the MOD_SECURITY module inside Apache. In prior variants of WordPress, it was a bug, however it was fixed back in form 2.8. So on the off chance that you are seeing this mistake in a later form of WordPress (we are running 3.2.1).
It is in all probability identified with your Apache web server joining the MOD_SECURITY module. So as to fix the issue you have to decide whether you have mod_security or mod_security2 introduced in light of the fact that the goals for every one of these modules is very unique.
MOD_SECURITY is an open source web application firewall:
That is introduced as a module for Apache-based web servers. There are two broadly utilized variants of the mod_security module, the main arrival of mod_security was out and out mod_security, the most recent discharge is alluded to as mod_security2. At the hour of this post the most recent arrival of mod_security is MODSecurity 2.6.
What Causes the HTTP Error:
As I referenced, our clients are running CentOS 5.7 with WHM and cPanel so the models you see here depend on that arrangement. Notwithstanding, you ought to have the option to apply our recommendations to your own condition on the off chance that you have a comprehension of your server working framework and the area of the server records for Apache and Mod_Security.
The HTTP Error is brought about by mod_security on the grounds that there is a security decide in mod_security that is activated by the WordPress Flash Uploader. This security rule is intended to stop realized security blemishes in Flash that have been abused to infuse code into your site. You can see this security rule trigger a message in your mod_security signs in WHM when you attempt to transfer a record utilizing the Flash Uploader. The message we were getting was the accompanying;
Access denied with code 406 (stage 2):
Exclusive Service on Fiverr by shafayat_studio
Example coordinate “^Shockwave Flash” at REQUEST_HEADERS:User-Agent. [file “/usr/nearby/apache/conf/modsec2.user.conf”] [line “203”] Your message might be distinctive dependent on the form of mod_security you have introduced. As should be obvious from our message.
It unmistakably expresses that the standard activated by the example coordinate was in the modsec2.user.conf document which helped us to verify that we had mod_security2 introduced. You will need to decide the mod_security that you have introduced and afterward apply the fix characterized in the fitting segment underneath.
MOD_SECURITY:
On the off chance that you have the prior adaptation of mod_security introduced, at that point it’s somewhat simpler to fix the HTTP Error for the Flash Uploader on the grounds that your progressions would all be able to be consolidated in the.htaccess record in your root index. This is one of the most befuddling parts of the fixes we found on the web on the grounds that not very numerous sites recognized the fixes among mod_security and mod_security2.
For mod_security you simply need to impair this standard for the async-upload.php document in your.htaccess record. You can do this by embeddings the accompanying order into your.htaccess record in the foundation of your site. To know more visit our official website http://bit.ly/2V80FDF
Deeify 