We just hit a serious problem in production. Our sites use cookies and some
of the cookies can be fairly large. When the cookie is less than about 2K,
it seems to work fine. But as soon as a cookie our site sends to the client
is 2K or over, the cookie doesn't make it through to the client.

I scurried to look through the docs and find MaxRequest where you can set a
max size for requests. We are not currently using this configuration option,
but the docs say that the default is unlimited in any case.

When we access our sites internally without going through pound, we do not
have this problem.

Help! Can someone offer advice on where to look?

Thanks!

Jay West
Knight's Direct

---
[This E-mail scanned for viruses by Declude Virus]

I had written...[...]
some[...]
client[...]

After poking around in the code, the issue was solved in development by
changing MAXBUF in pound.h from 2048 to 8192. Before I make that same change
to the production side of the house, can anyone tell me if increasing MAXBUF
by a factor of 4 may cause other problems I'm not aware of?

Thanks!

Jay West

---
[This E-mail scanned for viruses by Declude Virus]

On Friday 20 August 2004 20.02, Jay West wrote:[...]

There is no problem with increasing the MAXBUF to anything you wish - it may 
waste a bit of memory, but there are no other adverse effects.

There are serious issues with cookies which are 2K large. The session code 
keeps only the first 63 bytes and it may get badly confused, and the HTTP 
standard allows limiting lines up to 128 characters, so quite a few clients 
and proxies may choke on it.

While there are certain advantages to using such a large cookie (particularly 
a plea of temporary insanity would gain a lot of credibility) I would 
strongly suggest you look again at your design...[...]