This will become a new release tomorrow if noone finds any "brown paper bag" stuff by then.
have the regressions in Protocols.HTTP.Server been satisfactorily fixed? I've been too tied up with my own life lately to check them personally...
On Jan 26, 2006, at 6:40 AM, Peter Bortas (nu med mindre Opera) @ Pike (-) developers forum wrote:
This will become a new release tomorrow if noone finds any "brown paper bag" stuff by then.
very good... out of curiousity, is Protocols.HTTP.Server supposed to (or should it) support multipart encoded post variables? in the recent past it didn't seem to, so I just made some modifications to my local copy.
if they'd be useful, i can dig them out.
bill
On Thu, 26 Jan 2006, Martin Nilsson (Opera) @ Pike (-) developers forum wrote:
URL-encoded post variables? yes.
A multipart encoder would be another good addition to Protocols.HTTP, but if it's not available yet, let's not hold up any releases for it.
Lack of features is not likely to make me put a brown paper bag over my head before meeting users, so no chance of hold-up there.
I wasn't suggesting a hold up of more than an hour or two... but since there's a feeling that it's already in there (haven't actually tested it to verify it works, which may be another matter altogether).
Incidentally, there seems to be a lockup problem with using Protocol.HTTP.Server.SSLPort. It seems to stop responding after a few (<20) requests. It was originally reported by someone working on sTeam, and I've independently verified it. Anyone else experience this? I can provide sample code if there's any interest in looking at it.
Bill
Lack of features is not likely to make me put a brown paper bag over my head before meeting users, so no chance of hold-up there.
Can you make a small testcase? In that case please check it in at least in 7.7. There is something broken with the SSL part somewhere, but noone has built up the motivation to figure out exactly what yet.
If someone figures out and fixes that I will force out a new release within a week.
Yes, it is. Protocols.HTTP.Server is there so it's simple to write small HTTP servers, and all kinds of sending data to the server should be supported. :)
Pike 7.6.66 is now available as a new stable release.
I strongly encourage everyone to upgrade to avoid the "reference underflow in modify_shared_string()" bug. It's a very hard bug to debug when you get it, and it dissapears if you change your code a bit causing Heisen-bugs.
(I have not made a news item or updated the HTML version of the changelog on pike.ida.liu.se. Feel free to du this before I get around to it.)
Changes since Pike 7.6.50 ----------------------------------------------------------------------
Changes in Pike:
o Added support for chunked transfer encoding and handle unexpected multiple headers in HTTP.Server.Request. o Added support for "urlencoded" as an alias for "url-encoded" in HTTP.Server.Request. o Added callback support to Stdio.FakeFile. o Added iso_646.irv, iso_4873.dv and iso_4873 to charsets. o Added UCS-2 API support to Odbc. o Fixed some bugs in Protocol.HTTP.Server.HeaderParser. o Fixed decoding boolean datatype in Protocols.XMLRPC. o Fixed short names in Standards.XML.Wix. o Fixed time(0) to behave like time(), not time(1). This is considered a bugfix and does not have backward compatibility. o Allow _disable_callbacks and _enable_callbacks on closed fd's.
Other:
o Added compatibility for more odbc drivers. o Optimized XML.Tree simplenode creation. o Fixed reference underflow in modify_shared_string() o Fixed segfault when exiting uninitialized mutex keys. o Fixed segfault for two special cases of indexing unexisting stuff. o Fixed gc problem that could produce an error "gc_mark() called for thing in zap weak pass that wasn't marked before" in pikes compiled with rtldebug. o Fixed multiset node ref bugs that affected iterators when the multisets contain destructed objects. o Fixed out of C-stack errors when resizing unbalanced mappings.
Build fixes:
o Fixed win32 compilation. o Fixed detection of SDL.Joystick on win32 o Automaticly add Pike icon to win32 binary. o Fixed signal_handler compilation on OperBSD. o Fixed gcc 4.0 compatibility. o Added mmap PROT_EXEC support to MacOS X via MAP_ANON.
Binaries for Linux/PPC and Solaris/SPARC uploaded.
Binaries for Linux/x86 and Windows/x86 uploaded.
o Fixed win32 compilation.
And on that note... One bug we should fix is the current backend-socket misfeature on NT.
Sometimes when you start pike it fails to create the backend listen-socket (generally speaking, all socketpair_ultra sometimes fails) since NT thinks there has been enough sockets created in the last-whatever-the-timeperiod-is.
It's the famous 'anti-worm' 'feature' in XP service-pack 2.
Just retrying the socket creation (a few times) is usually enough.
o Added support for chunked transfer encoding and handle unexpected multiple headers in HTTP.Server.Request.
From .64 to .66 the function populate_raw() has been removed from
HTTP.Server.Request(). Why isn't that needed anymore? It seems strange that a previously needed function just get removed like that...
( I'm just wondering as I'm trying to search for some cause why my Roxen hangs every other day ("hangs" as in no CPU-usage and can only be killed with -9). And with Pike 7.6.64 it's working on another system, but it might of course be the system's and not Pike's fault. )
Why is that strange? It was an internal-only function that was not needed.
As nothing replaced it, it looked like it might have been removed by mistake.
But as it's not related to my problem, I guess I don't care.
:-). Jag kan kommentera.
Sätter du upp gula fina affischer någonstans, förresten? (Kom texten med där?)
Actually, something did replace it. The raw population is done in the normal parser.
Pike 7.6.66 is now available as a new stable release.
Could someone commit/add the attached files in Pike/7.6/packaging/fink ?
Thanx.
pike-devel@lists.lysator.liu.se