Bug 41391 - too long period setting makes max-age overflow
Summary: too long period setting makes max-age overflow
Alias: None
Product: Apache httpd-2
Classification: Unclassified
Component: mod_expires (show other bugs)
Version: 2.2.4
Hardware: Other All
: P4 minor (vote)
Target Milestone: ---
Assignee: Apache HTTPD Bugs Mailing List
Keywords: MassUpdate, PatchAvailable, RFC
Depends on:
Reported: 2007-01-17 06:47 UTC by Takashi Sato
Modified: 2018-11-07 21:08 UTC (History)
0 users

do not allow negetive value in max-age (1.11 KB, patch)
2008-08-13 14:08 UTC, rahul
Details | Diff
remove extra code. (1.85 KB, patch)
2008-08-14 03:34 UTC, rahul
Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Takashi Sato 2007-01-17 06:47:37 UTC
When too long period (about 68 years 1 month 6 days) is set to ExpiresDefault 
(or ExpiresByType), mod_expires adds a negative max-age to Cache-
Control. "modifier" on mod_expires.c Line 217 overflow.

How to reproduce:
enables mod_expires and add

ExpiresDefault "access plus 70 years"

to httpd.conf and restart the httpd. 
$ wget -S http://localhost/test.html

Cache-Control: max-age=-2087447296

Cache-Control: max-age=2207520000

I suggest modification of the overflow or adding "You shouldn't set a too long 
period" to the document.
Comment 1 rahul 2008-08-13 14:08:35 UTC
Created attachment 22444 [details]
do not allow negetive value in max-age

If it exeeds maxint, set it to maxint
Comment 2 rahul 2008-08-14 03:34:39 UTC
Created attachment 22445 [details]
remove extra code.
Comment 3 Rainer Jung 2018-02-25 20:08:39 UTC
Undo spam change
Comment 4 William A. Rowe Jr. 2018-11-07 21:08:19 UTC
Please help us to refine our list of open and current defects; this is a mass update of old and inactive Bugzilla reports which reflect user error, already resolved defects, and still-existing defects in httpd.

As repeatedly announced, the Apache HTTP Server Project has discontinued all development and patch review of the 2.2.x series of releases. The final release 2.2.34 was published in July 2017, and no further evaluation of bug reports or security risks will be considered or published for 2.2.x releases. All reports older than 2.4.x have been updated to status RESOLVED/LATER; no further action is expected unless the report still applies to a current version of httpd.

If your report represented a question or confusion about how to use an httpd feature, an unexpected server behavior, problems building or installing httpd, or working with an external component (a third party module, browser etc.) we ask you to start by bringing your question to the User Support and Discussion mailing list, see [https://httpd.apache.org/lists.html#http-users] for details. Include a link to this Bugzilla report for completeness with your question.

If your report was clearly a defect in httpd or a feature request, we ask that you retest using a modern httpd release (2.4.33 or later) released in the past year. If it can be reproduced, please reopen this bug and change the Version field above to the httpd version you have reconfirmed with.

Your help in identifying defects or enhancements still applicable to the current httpd server software release is greatly appreciated.