|  support |  documentation |  report a bug |  advanced search |  search howto |  statistics |  random bug |  login
Request #33623 History buffer in gzinflate
Submitted: 2005-07-09 15:08 UTC Modified: 2016-12-30 23:00 UTC
Avg. Score:5.0 ± 0.0
Reproduced:1 of 1 (100.0%)
Same Version:0 (0.0%)
Same OS:0 (0.0%)
From: vincent dot lascaux at centraliens dot net Assigned:
Status: Open Package: Zlib related
PHP Version: 5.0.4 OS:
Private report: No CVE-ID: None
View Add Comment Developer Edit
Anyone can comment on a bug. Have a simpler test case? Does it work for you on a different platform? Let us know!
Just going to say 'Me too!'? Don't clutter the database with that please — but make sure to vote on the bug!
Your email address:
Solve the problem:
31 - 3 = ?
Subscribe to this entry?

 [2005-07-09 15:08 UTC] vincent dot lascaux at centraliens dot net

I'm the autor of File_Archive ( and I'm adding a CAB file reader to it. This format can store deflated data, that can be uncompressed with gzinflate. Unfortunately, the data is cut blocks. The doc specifies that "Each block is flushed out of the compressor before the next block begins, so the last sub-block in each block will be marked as the ‘end’ of the stream. Any decoding trees are discarded after each block, with only the history buffer surviving from one block to the next."

My feature request is to be able to give to gzinflate the history buffer to use, and to retrieve from it the history buffer after the compression of the data.

A possible syntax would be
string gzinflate(string data[, int length[, array options]])
The array could store a reference to a history buffer that would be used (if not null) to uncompress the data and that would be updated after the data has been uncompressed.


Add a Patch

Pull Requests

Add a Pull Request


AllCommentsChangesGit/SVN commitsRelated reports
 [2016-12-30 23:00 UTC]
-Package: Feature/Change Request +Package: Zlib related
PHP Copyright © 2001-2020 The PHP Group
All rights reserved.
Last updated: Thu Nov 26 12:01:23 2020 UTC