15 Mar
2008
15 Mar
'08
3:31 a.m.
Jeremy wrote:
On Sat, Mar 15, 2008 at 01:22:09AM +0000, Jeremy Henty (ie. me) wrote:
I was wrong, the https filter dpi *is* starting. But, its debugging messages don't appear because it sends them to stdout, which dpid redirects to the DPI socket. This feels ... somehow ... wrong.
And so it is! (Patch submitted in a new thread.) After redirecting the debugging messages to stderr I see:
[https dpi]: {In https.filter.dpi} [https dpi]: ***Value of cmd, url or http_query is NULL - cannot continue [https dpi]: { exiting https.dpi}
which at least gives some idea of what is going wrong.
It appears that Capi_dpi_build_cmd() needs to test for "proto.https" instead of "https"...