[
https://issues.apache.org/jira/browse/SOLR-3238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13262074#comment-13262074
]
David Smiley commented on SOLR-3238:
------------------------------------
Since more of the UI is now actually loaded asynchronously, it is subject to
the jetty's DefaultServlet cacheing headers, which are non-existent by default.
I found it highly annoying today when I updated Solr to find that the UI
wasn't updated, even when I told my browser to force-reload. I had to clear my
browser cache. I looked into this a bit and I propose that
example/etc/webdefault.xml has the "cacheControl" piece of it be un-commented,
and set the max-age to 60 (in seconds). It is unlikely the timespan between a
browser requesting it and Solr being shut down, updated, redeployed, and the
browser fetches it again. Possible but unlikely. When this time span is
exceeded, a browser would re-request the resources but it would get back a
small 304 status to indicate the file hasn't changed, assuming it hasn't. To
be clear, this applies to the admin UI in the out-of-the-box jetty
configuration, and doesn't apply to searches. Sound good? I can commit it
trivially.
> Sequel of Admin UI
> ------------------
>
> Key: SOLR-3238
> URL: https://issues.apache.org/jira/browse/SOLR-3238
> Project: Solr
> Issue Type: Improvement
> Components: web gui
> Affects Versions: 4.0
> Reporter: Stefan Matheis (steffkes)
> Assignee: Stefan Matheis (steffkes)
> Fix For: 4.0
>
> Attachments: SOLR-3238.patch, SOLR-3238.patch, SOLR-3238.patch,
> solradminbug.png
>
>
> Catch-All Issue for all upcoming Bugs/Reports/Suggestions on the Admin UI
--
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
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
