Paul,
You can avoid OpenSSL errors by using curl as http library. IIRC I've
had same problem when accessing https over http proxy, that' was my
primary motivation to write libcurl patch.
I checked the ./configure --help and didn't see an option for
this. The SSL problem is one high on
Stipe,
which IPs do you mean Jonathan? The client (WAP device) IPs? I guess you
would have them in the wapaccess.log file logged. I'm not sure (without
code review) if "broken requests" are logged in wapaccess.log, but I
guess not.
Yeppers, the client ones. I just checked all of my l
I think I found the leak. I ran 2004-11-23 (and am still doing
so) without any leaks, but then if I run 2004-11-30 it leaks. I did a
diff between the two and there's just three minor changes. Attached is
the diff file, but note that it's backwards due to the way I did the
diff. (Ie. '-
Paul,
There are at least 2 ways to break concrete wall:
1. try to break concrete wall with your head
2. use more appropriate set of tools
I think curl does an excellent job, but I want to continue using
the official Kannel so I don't have headaches keeping up to date.
Thanks nonetheless
ignore.
Stipe
Hello all,
just to let you know that we have/had today problems with DNS resolving for the
kannel.org mailing lists.
Basically most MTAs should have been unable to deliver mail to the mailing
lists, due to a MX record for kannel.org that was pointing to a DNS no longer in
use (3glab.org).
Our
Jonathan Houser wrote:
Yeppers, the client ones. I just checked all of my logs, and the
only IPs I see regarding WAP are the ones from an IP I have blocked.
Regardless, it'd be very helpful if they were on the same line in the
same log as the fetch itself: correlating traffic is hard -- es
Stipe,
ok, go ahead. wapbox of course knows the remote client IP address. For an
example, see gw/wap-appl.c:760 where the alog() call is done to log the
request
to the wapaccess.log file.
I have the patch. I'll test it tomorrow morning and submit it if
it works. It was as easy as you
I've been using the WAP GW with a mobile which appends q-values to it's
'Accept:' headers in its WSP Connect meassage. I noticed that Kannel's
decoded q-value differs from the one the mobile sends. So far, this
would be a minor problem but in some cases, if the decoded q-value is
above 1000, Ka
Hello,
In wap/wtp_resp.h there are the following lines:
/*
* Nokia wap gw uses the size of 576, but mobiles use 1,5K size,
* I will think later what is better to use
*/
#define SAR_SEGM_SIZE 576
If I remember right because of that downloads are limited to ~140kb.
Is there some partic
10 matches
Mail list logo
