Re: [AOLSERVER] URL handling produce segfault

2011-07-05 Thread Gustaf Neumann
Alexey, both URLs work nicely for me (using 4.5.1 from sourceforge under Mac OS X); the URLs are rewritten finally into /?q=тавр*+2011 Can it be that you have some unusual encoding settings? -gustaf neumann On 04.07.11 11:54, Alexey Pechnikov wrote: 1. It's work fine:

Re: [AOLSERVER] URL handling produce segfault

2011-07-05 Thread Alexey Pechnikov
Thanks Gustaf, I'm sorry, the problem is in my binary tcl extension (full-text search extension for SQLite3 with Snowball stemmer support). Is it possible to prevent (or detailed logging) the AOL segfault in case of tcl extension segfault? I use runit supervisor and AOL is restarting

Re: [AOLSERVER] Problem with file uploads larger than maxinput

2011-07-05 Thread Fenton, Brian
Hello I've been struggling a little with this change. I took the HEAD version including Gustaf's changes and compiled it. When I uploaded a file larger than the max, I could see that it was calling Gustaf's new function Ns_ConnReturnEntityToLarge (correctly triggered by the E_CRANGE) -

Re: [AOLSERVER] URL handling produce segfault

2011-07-05 Thread Gustaf Neumann
a segfault is a segfault is a segfault no matter whether is happens in aolserver, in tcl or in an extension. you might have a chance to recover from segfaults in nsproxy, but certainly, the best approach is to get rid of these... -gn On 05.07.11 21:25, Alexey Pechnikov wrote: Is it

Re: [AOLSERVER] Problem with file uploads larger than maxinput

2011-07-05 Thread Gustaf Neumann
Strange, it works for me. can you send me your config file? Concerning the right place: As it was discussed here, it would be certainly better to move the reply-sending to a request handling thread (or a spooling thread like in naviserver), simply to be sure that the driver is never blocking.