You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@river.apache.org by "Mark Brouwer (JIRA)" <ji...@apache.org> on 2007/07/24 10:05:31 UTC
[jira] Updated: (RIVER-6) com.sun.jini.tool.ClassServer needs
support for Last-Modified and If-Modified-Since headers
[ https://issues.apache.org/jira/browse/RIVER-6?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mark Brouwer updated RIVER-6:
-----------------------------
Component/s: com_sun_jini_tool
Affects Version/s: jtsk_2.1
> com.sun.jini.tool.ClassServer needs support for Last-Modified and If-Modified-Since headers
> -------------------------------------------------------------------------------------------
>
> Key: RIVER-6
> URL: https://issues.apache.org/jira/browse/RIVER-6
> Project: River
> Issue Type: Improvement
> Components: com_sun_jini_tool
> Affects Versions: jtsk_2.1
> Reporter: Mark Brouwer
> Priority: Minor
>
> Given the fact ClassServer is the number one codebase server in the world one might expect it to provide a bit more support for the response header {{Last-Modified}} and the request header {{If-Modified-Since}}.
> While the lack of these might not be very harmfull for JVMs that have the default {{jar}} protocol handler, some containers providing a more advanced caching mechanism for JAR files can make effective use of these headers.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.