Obviously anything that is resolved with editing your httpd.conf is not specific to just WordPress. There are two major reasons why I posted that here:
- Tons and tons of www.remarpro.com users were having the same issue, and would likely search here for solutions
- Most (and I’m using that term conservatively) people are not web developers or designers and may only be using WordPress, so wouldn’t experience this problem in any other fashion.
Lastly, if you would have read my post thoroughly, I said in the “Supporting Evidence” section:
This tells me that it is specific to the site, not the hosting provider, or even WordPress.
(That is to say, its NOT a wordpress issue, but a site issue. Site as is defined within your httpd.conf file, something that wordpress obviously never changes.)
Technically it’s not specific to the host, but to the site, because you can have multiple sites configured within one host (as I do) and have different directives for each site, with different options.
