Re: Length Incosistency Between FCGI_RECORD and FCGI_PARAMS

Jon Ribbens <jon+fastcgi-developers-JgzTmhv+UHffC7kMvaharFpr/1R2p/[email protected]>
Newsgroups gmane.comp.web.fastcgi.devel
Message-ID <[email protected]>
On Fri, Jan 30, 2009 at 02:27:19PM +0200, Volkan YAZICI wrote:
> Whole record length is represented by 2 bytes (maximum 2^(2*8) bytes),
> but a key+value length might be representing a block of 8 bytes (maximum
> 2^(4*8) bytes) in size.
> 
>   +-----------------------------+
>   | ### FCGI_RECORD ########### |
>   | +----------------------------------------------+
>   | | ### FCGI_PARAMS ############################ |
>   | +----------------------------------------------+
>   +-----------------------------+
> 
>   ^                             ^                  ^
>   |---- 2^(2*8)=65536 bytes ----|                  |
>   |--------------- 2^(4*8)=4294967296 -------------|
> 
> How can this be possible? I have read FastCGI specification[1] over and
> over again but couldn't find a clue. Would you mind helping me to
> clarify this point please?

Sorry, but in what way is "so don't do that then" not an answer to
your question?
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.