]
Brian Leathem commented on RF-11888:
------------------------------------
Brendan, there are two paths forward:
# close this ticket as the RichFaces version in thi URL is sufficient for your use case
# add a version (v) attribute to the list of attributes pared by the ResourceServlet
Since you opened this ticket, can you indicate which direction you would prefer it to
proceed?
Resource Servlet can't handle query string appended to resource
url
-------------------------------------------------------------------
Key: RF-11888
URL:
https://issues.jboss.org/browse/RF-11888
Project: RichFaces
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: resource handling
Affects Versions: 4.1.0.Final
Environment: Glassfish 3.1.1 (NO Tomcat)/Mojarra 2.1.3 Chrome browser -
Reporter: Brendan Healey
Priority: Critical
Labels: waiting_on_user
A custom resource handler (
http://blogs.oracle.com/rlubke/entry/jsf_2_0_new_feature)
can be used to append a version string (i.e. ?v=23) to a resource url to force a
browser to refresh a resource rather than use any cached version.
At present any appending of a version string causes a 404 response status, for example:
Request URL:
https://localhost:8181/MyApp/org.richfaces.resources/javax.faces.resource...
Removing the url parameter makes it work ok. As you can see I have resourceMapping
enabled.
This is essential to cause a browser to issue a request to the server if a static
resource is held in a browser cache and is not expired, but you've upgraded the
richfaces version. You have to have a way to invalidate the cache, and I'm not
seeing how this can be done in a sensible way. You can set the Cache-Control
no-cache header, but I'd need to do this in a way that says "I've just
upgraded
richfaces, so don't use the cache, issue a request to the server for the resource,
but cache the result and use this until the next time".
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: