This is a discussion on mod_proxy on windows not working (but works on another one) within the Apache Web Server forums, part of the Web Server and Related Forums category; Hello. I'm trying to set up a remote Windows machine like I have my local one set up. The ...
|
|||||||
| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
|
|||
|
Hello. I'm trying to set up a remote Windows machine like I have my
local one set up. The local one works, the remote one doesn't. I'm setting up a reverse proxy in httpd.conf, and the proxied url produces the following error: proxy: No protocol handler was valid for the URL /fb_stock_demo/ stockList. If you are using a DSO version of mod_proxy, make sure the proxy submodules are included in the configuration using LoadModule. In httpd.conf, I have mod_proxy, mod_proxy_connect and mod_proxy_http all enabled (I uncommented those lines). I also have tried specifying the absolute paths for the modules instead of the relative "modules/ mod_proxy_http.so" etc. But it still gives me this error, as if I'd made no change. It's as if it isn't really enabling the sub-modules, but wouldn't it complain if it couldn't load them? Thanks for any help. I'm on a deadline for Monday and this very frustrating detail is holding up the rest of the project. - Jake |
|
|||
|
Actually, this may be simpler than that. I'm not sure that the
httpd.conf belongs to the apache process running. Apparently there's another one running and I wasn't aware of it. So the answer is I'm a fool. On May 4, 12:03 am, jakemiles <jacob.mi...@gmail.com> wrote: > Hello. I'm trying to set up a remote Windows machine like I have my > local one set up. The local one works, the remote one doesn't. I'm > setting up a reverse proxy in httpd.conf, and the proxied url produces > the following error: > > proxy: No protocol handler was valid for the URL /fb_stock_demo/ > stockList. If you are using a DSO version of mod_proxy, make sure the > proxy submodules are included in the configuration using LoadModule. > > In httpd.conf, I have mod_proxy, mod_proxy_connect and mod_proxy_http > all enabled (I uncommented those lines). I also have tried specifying > the absolute paths for the modules instead of the relative "modules/ > mod_proxy_http.so" etc. But it still gives me this error, as if I'd > made no change. It's as if it isn't really enabling the sub-modules, > but wouldn't it complain if it couldn't load them? > > Thanks for any help. I'm on a deadline for Monday and this very > frustrating detail is holding up the rest of the project. > > - Jake |