Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bug fix for extremely large index files #1

Open
wants to merge 91 commits into
base: master
Choose a base branch
from

Conversation

lucianpls
Copy link
Member

One of the commits fixes a but that appears when the index per level is larger than 2GB.

Module will use an updated configuration if one exists in the request…
The gzipped content gets sent as such if the request headers declare support for gzip
Otherwise, mod_deflate is used to inflate the content.
If mod_deflate is not found when needed, a warning is issued
Visual Studio project updated to VS2017
c->size.z is 64bit, which will promote the math to 64bit, signed.
This is safe until the index file is under 2^63 - 1 bytes.
libpar-2 is still in dev, but it seems to work fine
- Use the subrequest filter stack for receive instead of the main request.  This allows stacking of filters
- Clean up the subrequest when done
Retry fetching data from remote source when the initial request fails.
The number to set is in addition to the first fetch.  By default it will try 5 times.
Is this even necessary?
When set, the module only responds to internal subrequests
Makes more sense to have the indirect flag in the httpd configuration.

Also moved the index read in a separate function
MRF_RegExp appears in the apache configuration, not in the control file
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant