[MAGNOLIA-2448] Incorrect handling of If-Modified-Since request header Created: 23/Oct/08  Updated: 23/Jan/13  Resolved: 22/Jan/09

Status: Closed
Project: Magnolia
Component/s: cache
Affects Version/s: 3.6.3
Fix Version/s: 4.0, 3.6.4, 3.6.5

Type: Bug Priority: Major
Reporter: Jon Barber Assignee: Magnolia International
Resolution: Fixed Votes: 1
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

ALL


Attachments: File Fix_for_if-modified-since_handling.patch    
Issue Links:
relation
Template:
Patch included:
Yes
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Testcase included:
Yes
Date of First Response:

 Description   

We are using Magnolia CE 3.6.3 and we have an issue with handling
if-modified-since headers. To illustrate :

jon@ubuntu:~/tests$ wget --header='If-Modified-Since: Tue, 1 Jan 2008 19:58:25 GMT' http://localhost:8180/magnoliaPublic/help/services.html
-16:35:59- http://localhost:8180/magnoliaPublic/help/services.html
=> `services.html'
Resolving localhost... 127.0.0.1
Connecting to localhost|127.0.0.1|:8180... connected.
HTTP request sent, awaiting response... 304 Not Modified
16:36:39 ERROR 304: Not Modified.

So basically magnolia is saying content has not been modified since Jan
1st this year, which is just plain wrong.



 Comments   
Comment by Magnolia International [ 23/Oct/08 ]

Thanks, awesome ! Will look into this a.s.a.p
Extra kudos for writing testcases!

Comment by Magnolia International [ 22/Jan/09 ]

Patch applied on 3.6 branch and trunk (4.0) Thanks a lot !

Generated at Mon Feb 12 03:36:49 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.