On Mon, 27 May 2002, Oliver Fromme wrote: > - Oops fails always. It logs "TCP_ERROR/555". I have no > idea what that means. In oops.log I find lines like > this (broken up for readability): > Mon May 27 10:33:09 2002 [0x88ad800]add_request_av(): \ > Invalid request string: valArray=%2C%2C%2C%2C%2C%2C%2C%\ > 2C%2C%2C&numArray=&meetArray=&i=11&de=0&ce=0&version=WI\ > N+5%2C0%2C41%2C0 >
This can mean two things: 1) buggy request (not compliant with RFC) 2) bug in oops request parsing. > As I said above, I will try to get some sample code set up > on a public accessible web site, so I can debug it (or > somebody else can have a look at it). I'd really like to > know what's going on there. > > If I can get a complete tcpdump log of such a failed re- > quest, would that be useful for someone to debug the pro- > blem? Yes, hexdump of packets for failed request is exactly what I need. > > Regards > Oliver Fromme > > -- > Oliver Fromme, secnetix GmbH & Co KG, Oettingenstr. 2, 80538 M�nchen > Any opinions expressed in this message may be personal to the author > and may not necessarily reflect the opinions of secnetix in any way. > > "All that we see or seem is just a dream within a dream" (E. A. Poe) > ===================================================================== > If you would like to unsubscribe from this list send message to > [EMAIL PROTECTED] with "unsubscribe oops-eng" in message body. > Archive is accessible on http://lists.paco.net/oops-eng/ > Igor Khasilev | PACO Links, igor at paco dot net | ===================================================================== If you would like to unsubscribe from this list send message to [EMAIL PROTECTED] with "unsubscribe oops-eng" in message body. Archive is accessible on http://lists.paco.net/oops-eng/
