You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Daniel Lipski (JIRA)" <ji...@apache.org> on 2012/05/04 11:14:49 UTC
[jira] [Created] (WICKET-4531) Last modified token not added to
resource name.
Daniel Lipski created WICKET-4531:
-------------------------------------
Summary: Last modified token not added to resource name.
Key: WICKET-4531
URL: https://issues.apache.org/jira/browse/WICKET-4531
Project: Wicket
Issue Type: Bug
Components: site
Affects Versions: 1.5.6
Environment: Windows Xp sp 3, Google Chrome 20.0.1123.4 dev-m, Apache Tomcat-7.0.25, JDK 1.6.30
Reporter: Daniel Lipski
When file system path to resource reference (file) contains space " " version token is not appended to its name. File is still accessible via web browser.
I think that problem is with encoding space with %20 and later when lastModified date is calculated for this file %20 is not decoded to space and file system could not find file.
When lastModified is not calculated for resource versioning token is not added to file name.
Regards
Daniel
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (WICKET-4531) Last modified token not added to
resource name.
Posted by "Daniel Lipski (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-4531?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Daniel Lipski updated WICKET-4531:
----------------------------------
Component/s: (was: site)
wicket
> Last modified token not added to resource name.
> -----------------------------------------------
>
> Key: WICKET-4531
> URL: https://issues.apache.org/jira/browse/WICKET-4531
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Affects Versions: 1.5.6
> Environment: Windows Xp sp 3, Google Chrome 20.0.1123.4 dev-m, Apache Tomcat-7.0.25, JDK 1.6.30
> Reporter: Daniel Lipski
>
> When file system path to resource reference (file) contains space " " version token is not appended to its name. File is still accessible via web browser.
> I think that problem is with encoding space with %20 and later when lastModified date is calculated for this file %20 is not decoded to space and file system could not find file.
> When lastModified is not calculated for resource versioning token is not added to file name.
> Regards
> Daniel
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (WICKET-4531) Last modified token not added to
resource name.
Posted by "Peter Ertl (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-4531?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Peter Ertl resolved WICKET-4531.
--------------------------------
Resolution: Duplicate
this should already be fixed with WICKET-4509
> Last modified token not added to resource name.
> -----------------------------------------------
>
> Key: WICKET-4531
> URL: https://issues.apache.org/jira/browse/WICKET-4531
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Affects Versions: 1.5.6
> Environment: Windows Xp sp 3, Google Chrome 20.0.1123.4 dev-m, Apache Tomcat-7.0.25, JDK 1.6.30
> Reporter: Daniel Lipski
>
> When file system path to resource reference (file) contains space " " version token is not appended to its name. File is still accessible via web browser.
> I think that problem is with encoding space with %20 and later when lastModified date is calculated for this file %20 is not decoded to space and file system could not find file.
> When lastModified is not calculated for resource versioning token is not added to file name.
> Regards
> Daniel
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira