For awhile I had been using an unmodified apache config along side the
webkit.cgi to test my side and develop servlets. It worked great,
accessing from 127.0.0.1/cgi-bin/webkit.cgi/
A few days ago, I got to the point where I was ready to deploy what I
had written on my root webserver documents directory.
I followed the webkit install / users manual, getting mod_webkit
installed and working correctly.
To my httpd.conf I added these lines:
LoadModule webkit_module libexec/httpd/mod_webkit.so
AddModule mod_webkit.c
<Location /wk>
WKServer localhost 8086
SetHandler webkit-handler
</Location>
I could now access webware from 127.0.0.1/wk, but once I got that
working, I tried to have it handle all requests to 127.0.0.1 through
webkit. I changed the config file to <Location /> which I believed
should work. It didn't.
If I went to the default page, the server seemed to go into a loop,
forwarding me to /, then //, ///, and so on. If I tried to access a page
directly, such as GeneralPage in the root directory, then it would
forward to the default webware location under the url
127.0.0.1/GeneralPage.py/ From that point forward, all urls were based
upon that, so when it tried to access the location I wanted, it was
appended to that incorrect url and would report not found.
I'm sure I've got something screwed up in either my apache config or one
of the webkit/appserver configs. Anyone spot a possible cause from the
effects I've described? I can provide copies of the configs and logs if
someone would be willing to check them out for me.
Thanks for any help you can give.
|