Hi all,

When running pound from the the current Debian/Ubuntu package (2.4.3), i get
errors when cookie data exceeds a certain length. The issue isn't present in
version 2.4.4, which i hand-compiled. Is this a known bug in older versions? I
couldn't find anything about it in the changelog.

To test the issue, i did something like
'wget --load-cookies cookie.txt http://127.0.0.1:8081'
where Pound was running at port 8081, of course.
The file cookies.txt looked like this:
127.0.0.1	FALSE	/	FALSE	0	c_id_test	{data}
Note that this should be tab-separated.

The server behind pound (in my case, a Zope/Plone site) would print the cookies
it gets on a terminal or in the log.

Whenever {data} exceeds a certain length (tried with a 1000-character string),
the server doesn't see any cookies. This also happens if there are several
shorter cookies whose combined lengths exceeds a value of roughly 500
characters.

The cookies are not removed on the client, only on the web server side of
pound.

Regards,

Kees

I think the default used to be smaller, I had to change this a while
back as well.  I changed it in the source code, but there appears to be
a compile directive for it.

Here are some previous posts about it.

http://www.apsis.ch/pound/pound_list/archive/2008/2008-02/1203715523000

Here's a sample pulled from the 'net (haven't tried it lately, it's been
a while).


make clean 
./configure --with-maxbuf=8192
make 
make install  



-----Original Message-----
From: Kees Hink [mailto:hink(at)gw20e.com] 
Sent: Thursday, June 11, 2009 4:43 AM
To: pound(at)apsis.ch
Subject: [Pound Mailing List] disappearing cookies with Pound 2.4.3

Hi all,

When running pound from the the current Debian/Ubuntu package (2.4.3), i
get errors when cookie data exceeds a certain length. The issue isn't
present in version 2.4.4, which i hand-compiled. Is this a known bug in
older versions? I couldn't find anything about it in the changelog.

To test the issue, i did something like
'wget --load-cookies cookie.txt http://127.0.0.1:8081'
where Pound was running at port 8081, of course.
The file cookies.txt looked like this:
127.0.0.1	FALSE	/	FALSE	0	c_id_test	{data}
Note that this should be tab-separated.

The server behind pound (in my case, a Zope/Plone site) would print the
cookies it gets on a terminal or in the log.

Whenever {data} exceeds a certain length (tried with a 1000-character
string), the server doesn't see any cookies. This also happens if there
are several shorter cookies whose combined lengths exceeds a value of
roughly 500 characters.

The cookies are not removed on the client, only on the web server side
of pound.

Regards,

Kees


--
To unsubscribe send an email with subject unsubscribe to pound(at)apsis.ch.
Please contact roseg(at)apsis.ch for questions.

--
This message has been scanned for viruses and dangerous content by
SecureMail, and is believed to be clean.