DO NOT REPLY [Bug 46895] New: Caching documents from ant.apache.org requires additional HTTP headers

[bu...@apache.org]

https://issues.apache.org/bugzilla/show_bug.cgi?id=46895

           Summary: Caching documents from ant.apache.org requires
                    additional HTTP headers
           Product: Ant
           Version: 1.7.1
          Platform: All
               URL: http://ant.apache.org/manual/index.html
        OS/Version: Linux
            Status: NEW
          Severity: minor
          Priority: P2
         Component: Documentation
        AssignedTo: notifications@ant.apache.org
        ReportedBy: Martin.vGagern@gmx.net


It seems that the HTML files served by ant.apache.org lack headers required for
caching, like ETag [1] or Last-Modified [2]. This has the effect that these
documents are not cached by most proxies or browsers, so that they have to be
requested over and over again, causing unnecessary server load as well as
annoying delays for clients.

I have initially observed this with the ivy manual, but later confirmed it for
other parts of the ant pages, like the manual. My transfers are usually
compressed using gzip, but I could also reproduce this with compression
disabled. I could also reproduce it using both HTTP/1.0 and HTTP/1.1.

Only HTML files seem to be affected, images are delivered with a lot of
caching-relevant headers, ETag and Last-Modified among them. I assume that the
images are served directly from their files, while the html files undergo some
processing, or are generated from a data base. Maybe you could tune this
process in such a way as to still provide Last-Modified and/or ETag?

If I can help with this in some way, like providing some network traffic dump
or having a look at server side scripts, please let me know.

[1] http://tools.ietf.org/html/rfc2616#section-14.19
[2] http://tools.ietf.org/html/rfc2616#section-14.29

-- 
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

DO NOT REPLY [Bug 46895] Caching documents from ant.apache.org requires additional HTTP headers

[bu...@apache.org]

https://issues.apache.org/bugzilla/show_bug.cgi?id=46895





--- Comment #2 from Martin von Gagern <Ma...@gmx.net>  2009-04-09 07:18:36 PST ---
(In reply to comment #1)
> This is because we use SSI to always contain the ad for the latest and greatest
> ApacheCon.

I see - at least for the start page and ivy docs. The ant manual doesn't seem
to contain that kind of banner.

> We probably could make the SSI part set proper cache headers to allow caching
> for a day or so (no idea how, though) - or re-try an iframe approach for the
> banner now that browsers have evolved a bit.

I'm in favour of the latter. Should be less work, better results due to longer
caching, and reduce the load on the webserver to boot, as you can avoid the SSI
processing.

Just a thought for a third, low-tech alternative: How about having some
redirect URLs for latest image and latest link target? You could hardcode those
URLs into the pages, and simply change image and conference pages they redirect
to.

-- 
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

DO NOT REPLY [Bug 46895] Caching documents from ant.apache.org requires additional HTTP headers

[bu...@apache.org]

https://issues.apache.org/bugzilla/show_bug.cgi?id=46895


Stefan Bodewig <bo...@apache.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
          Component|Documentation               |Other
         OS/Version|Linux                       |All




--- Comment #1 from Stefan Bodewig <bo...@apache.org>  2009-04-09 07:03:17 PST ---
This is because we use SSI to always contain the ad for the latest and greatest
ApacheCon.

We probably could make the SSI part set proper cache headers to allow caching
for a day or so (no idea how, though) - or re-try an iframe approach for the
banner now that browsers have evolved a bit.

-- 
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.