I found a fix for this issue.
A line in the config was not liked by the wonder adaptor. In
/ets/apache2/sites-available/default-ssl:
SSLOptions +FakeBasicAuth +ExportCertData +StrictRequire
On our test platform, were everything worked, this was commented-out. So the
problem,
On Jul 12, 2012, at 12:22 PM, Klaus Berkling wrote:
Next up, debugging an apache module...
So I'm setting up an Ubuntu development environment to debug the adaptor (whoo
hoo).
Kieran, I'm going to need that C book. :-)
Should I use the integration or master branch? Is someone doing work on
Le 2012-07-13 à 14:36, Klaus Berkling a écrit :
On Jul 12, 2012, at 12:22 PM, Klaus Berkling wrote:
Next up, debugging an apache module...
So I'm setting up an Ubuntu development environment to debug the adaptor
(whoo hoo).
Kieran, I'm going to need that C book. :-)
Should I use
Greetings Klaus,
That is great. I am kind of stuck with CentOS. I am still having to follow up
on the little SELinux part to enable it to share its web site to the outside
world. Apparently, the little line on the bottom of the wocommunity
instructions does not get job done. It works from
Hi All.
Some of you might remember me writing about this issue during WOWODC. I'm
restarting the thread because I still can't find a solution. I get the
following error when making https requests to one of our apps (no problem with
static html pages):
Did not receive any response from
Hi Klaus,
I can't add much. The problem is in the adaptor. I'd focus on the first error
sendBuffers(): send error: Bad address and consider the rest to be symptoms.
Other than adding some logging messages to the adaptor, I have no ideas or
pointers.
Next up, debugging an apache module...
On Jul 12, 2012, at 1:09 PM, Chuck Hill wrote:
I can't add much. The problem is in the adaptor. I'd focus on the first
error sendBuffers(): send error: Bad address and consider the rest to be
symptoms. Other than adding some logging messages to the adaptor, I have no
ideas or pointers.
On 2012-07-12, at 1:33 PM, Klaus Berkling wrote:
On Jul 12, 2012, at 1:09 PM, Chuck Hill wrote:
I can't add much. The problem is in the adaptor. I'd focus on the first
error sendBuffers(): send error: Bad address and consider the rest to be
symptoms. Other than adding some logging
