If mod_proxy was compiled as a general module, it requires that you also explicitly load the corresponding submodules. It is possible that mod_proxy_http not enabled on your server, which leads to an internal server error when mod_proxy tries to process the request passed to it by mod_rewrite .
mod_proxy itself is turned on, as you said, and probably works, because if you donβt have it, using the P flag will generate a 404 response. It's hard to know for sure, although without an error log, so you need to find someone with access to it to find out what is happening to help you solve the problem.
Tim stone
source share