My last message was in error. The error box was not displaying on the
browser, but on the server. However, I believe I discovered the problem
with wkcgi.exe. My log files showed a get instead of a post, a change in
behavior from the webkit.cgi and mod_webkit. The webkit.cgi and mod_webkit
for Windows handled a large amount of data in a form tag that did not
explicitly say method=post (on oversight on my end, but because I received
no error, I did not know to place it in). However, the wkcgi.exe caused an
exception on the server. I am not sure what the default behavior is
supposed to be, but once I placed in method=post on my form tag, everything
Thanks for all the help.
From: Geoff Talvola [mailto:gtalvola@...]
Sent: Thursday, October 11, 2001 2:15 PM
Subject: RE: [Webware-devel] cvs update
At 01:46 PM 10/11/01 -0700, you wrote:
>I tried the new wkcgi.exe, but I still had problems when I tried to
>forwardRequest. I have attached the code examples just in case. This
>examples, after I click forward, eventually timesout. Is there a special
>directory I need to place the wkcgi.cfg in?
A few things:
- The config file should be called webkit.cfg, not wkcgi.cfg. It should be
in the same directory as wkcgi.exe. But, if you are running the app server
on the standard port 8086, you don't even need a webkit.cfg at all.
- It works properly for me, using your test psp files. Are you sure you
were using the new version of wkcgi.exe?
- I found a different bug though -- if the webkit.cfg is missing, then
wkcgi.exe dumps out some extra text into the output. I've fixed it and
attached yet another compiled gzipped version of wkcgi.exe here. Try this
and see if it works for you.
- Geoff Talvola