You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@tapestry.apache.org by "Antoine Lochet (JIRA)" <ji...@apache.org> on 2010/05/06 12:14:51 UTC
[jira] Updated: (TAP5-1133) app-version in URL should be disabled
when in production-mode
[ https://issues.apache.org/jira/browse/TAP5-1133?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Antoine Lochet updated TAP5-1133:
---------------------------------
Description:
The app-version added in the URL for static elements which is convenient is development mode to avoid browser caching.
We have a trouble in production when Tapestry is behind load-balancers.
One request can fail (error 404) if it arrives on a different server after a first request on another server.
This should be desactivated in production-mode to avoid such errors.
Or at least make an fixed default app-version when in this porduction-mode.
was:
The app-version added in the URL for static elements which is convenient is development mode to avoid browser caching.
We have a trouble in production when Tapestry is behind load-balancers.
One request can fail (error 404) if it arrives on a different server after a first request on another server.
This should be desactivated in production-mode to avoid such errors.
Priority: Minor (was: Major)
> app-version in URL should be disabled when in production-mode
> -------------------------------------------------------------
>
> Key: TAP5-1133
> URL: https://issues.apache.org/jira/browse/TAP5-1133
> Project: Tapestry 5
> Issue Type: Improvement
> Components: tapestry-core
> Affects Versions: 5.1.0.0, 5.1.0.1, 5.1.0.2, 5.1.0.3, 5.1.0.4, 5.1.0.5, 5.1.0.6, 5.1.0.7
> Reporter: Antoine Lochet
> Priority: Minor
>
> The app-version added in the URL for static elements which is convenient is development mode to avoid browser caching.
> We have a trouble in production when Tapestry is behind load-balancers.
> One request can fail (error 404) if it arrives on a different server after a first request on another server.
> This should be desactivated in production-mode to avoid such errors.
> Or at least make an fixed default app-version when in this porduction-mode.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.