The source indicates that this message comes up if there are more
than MAXHEADERS headers (either in the request or in the response),
and MAXHEADERS is 128 by default.
However going very quickly through the source, I see no handling of
multi-line headers (with continuation lines starting with a space or
tab), which would lead to 2 problems:
- some funnily-formated (but correct) headers (with a newline and a
space very shortly after the beginning, such as right after the :)
would not be correctly interpreted by pound
- each additional line in a multi-line header would count towards the
MAXHEADERS limit, so for very very long headers you might indeed have a problem
Can someone confirm/infirm this?
I have to admit though that I don't understand why if you're using a
DB to store your session data, you would have very large headers? A
very simple cookie to store a session ID should be enough, and would
save you and the user quite a bit of bandwidth (think that such large
cookies will be sent for every single request, even static files such
as pictures etc!).
Jacques.
At 17:30 28/07/2009, Benedikt Nießen wrote:
Hi,
How to interpret this message? When I have a big header in a
PHP-Script (handling sessions via database => no 4KB limit) I get
"Too many headers" in the logs and an e500 displayed.
Robert said it would not be the header size but, what is it? Without
pound it works fine.
Any hints?
Thanks,
Ben.
See all the ways you can stay connected to friends and family
_________________________________________________________________
More than messagescheck out the rest of the Windows Live.
http://www.microsoft.com/windows/windowslive/
--
To unsubscribe send an email with subject unsubscribe to [email protected].
Please contact [email protected] for questions.
--
To unsubscribe send an email with subject unsubscribe to [email protected].
Please contact [email protected] for questions.
