[MAGNOLIA-1913] Content-Length not set properly for top site url Created: 03/Dec/07  Updated: 27/Nov/13  Resolved: 07/Jul/08

Status: Closed
Project: Magnolia
Component/s: cache
Affects Version/s: 3.5 RC2
Fix Version/s: None

Type: Bug Priority: Major
Reporter: Jan Haderka Assignee: Jan Haderka
Resolution: Outdated Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: Text File curlOutput.txt    
Issue Links:
relation
is related to MAGNOLIA-2127 New Cache features and api Closed
Template:
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

 Description   

When accessing top url of any magnolia powered site, content length in http header is set to 0. This seems to be cause of problems for some robots (e.g. digg content digester).
Length is set properly when using concrete page url.
See attached curl output for details.



 Comments   
Comment by Jan Haderka [ 07/Jul/08 ]

Fixed as part of new cache. Content-length header field is no longer set for redirects. It is set only for content delivery and then it is set to correct length.

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